RESOLVED FIXED 44306
Web Inspector: resources css files improvements - editing and ordering. 
https://bugs.webkit.org/show_bug.cgi?id=44306
Summary Web Inspector: resources css files improvements - editing and ordering.
Adam
Reported 2010-08-19 16:40:07 PDT
It would be nice to be able to edit the styles directly when viewing the full style sheet after clicking it's location from the elements styles section. This is currently possible in FireBug. Also the resources css section seems to combine two functions that don't seem to go hand in hand. It displays the css files in the order they were downloaded. While checking on resources and speed and such, this is convenient. OTOH, when viewing the style sheets to edit them or find where a style is, being sorted by download order is useless. They should be grouped by location then alphabetically, it would hold more context that way. FireBug has resource tracking, but it doesn't couple it with css editing. This allows for being able to view the css while editing it at anytime, without needing to enable the resource heavy resource tracking.
Attachments
Add attachment proposed patch, testcase, etc.
Pavel Feldman
Comment 1 2010-08-19 23:28:55 PDT
All good points. Talking about enabling resource tracking for CSS traceability. That was also on our to-do list. In fact, we don't really need resource tracking for that, just a technical difficulty that needs to be resolved. We were going to edit styles in the 'Locally modified' tab next to Headers and Contents tabs, still in the resources panel. I agree with your concern, but I don't see a solution that would satisfy everybody. Splitting resources tab into 'network log' tab and 'resource browser' tab would be nice, but we already have way too many tabs. Timothy, given that we start editing CSS and JavaScript, this could be a valid excuse for a panel. What do you think?
Alexander Pavlov (apavlov)
Comment 2 2011-11-11 06:26:22 PST
*** Bug 62715 has been marked as a duplicate of this bug. ***
Alexander Pavlov (apavlov)
Comment 3 2011-11-18 02:08:15 PST
(In reply to comment #2) > *** Bug 62715 has been marked as a duplicate of this bug. *** This bug was a wrong target duplicate for 62715, fixed.
Note You need to log in before you can comment on or make changes to this bug.