It’s quite frequently that an HTML/CSS designer might want to make changes to a live web page. Maybe she doesn’t have write access, or maybe the fixes needed aren’t worth the start-up cost of copying the page locally and working on it there, or multiple designers want to work up ideas on a given page simultaneously. The “Inspect Element” capabilities of most modern browsers will let you make HTML/CSS changes to a live page, but navigating or refreshing causes those changes to be lost, and they’re hard to keep track of.
Here’s a feature wishlist:
- keep track of “Inspect Element” user changes with the ability to save them locally
- keep changes in discrete “changesets” that can be re-applied, or saved as a unified patch of the original files, or at least as the modified original files
- allow swapping page CSS files with user-controlled CSS files (e.g. file:/// or htttp://localhost/)
- allow swapped CSS files to be periodically “refreshed” so the user wouldn’t have to switch between CSS editor and browser.
You can manually do (3) and use the CSS Reload Every bookmarklet, but it reloads all CSS, which is kinda of jarring.
A bookmarklet could implement (3) and (4) and persist its settings in a cookie.
Update: Here’s a bookmarklet that let’s you swap CSS files and stores its settings in a cookie for the current page. Next step is for it to allow adding files and controlling the cookie path.