Open
Bug 771206
Opened 12 years ago
Updated 2 years ago
[style editor] re-apply the modified stylesheets when the page is reloaded.
Categories
(DevTools :: Style Editor, enhancement, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: paul, Unassigned)
References
(Blocks 1 open bug)
Details
No description provided.
Reporter | ||
Updated•12 years ago
|
Priority: -- → P1
Comment 2•12 years ago
|
||
This does not seem to be a toolbox regression. It is related to dead access to reloaded contentWindow, most probably due to the strict access rules introduced in Firefox 17. Should this still be bocking 816946
Comment 3•12 years ago
|
||
Yes, it should ... that list is not only for toolbox regressions, it is a list of things we need to fix before Firefox 20 is released.
Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Girish Sharma [:Optimizer] from comment #2) > This does not seem to be a toolbox regression. It is related to dead access > to reloaded contentWindow, most probably due to the strict access rules > introduced in Firefox 17. Because of the Toolbox, the StyleEditor needs to support page reloading.
Updated•12 years ago
|
Assignee: nobody → fayearthur
Updated•12 years ago
|
Blocks: DevToolsPaperCuts
Reporter | ||
Comment 5•12 years ago
|
||
Heather, do you think we can get that into Firefox 20?
Flags: needinfo?(fayearthur)
Comment 6•12 years ago
|
||
(In reply to Paul Rouget [:paul] from comment #5) > Heather, do you think we can get that into Firefox 20? I wasn't planning on it, because it seemed like a problem with a lot of edge cases. Which is why I was advocating bug 826982 for 20. This is my main priority right now though, so maybe? The big edge case is if the file changes on disk or the server and the changes no longer apply cleanly upon refresh. My thoughts were to get a diff of changes before the page reloads, if the changes no longer apply, offer an option to export it as a diff or just revert the files.
Flags: needinfo?(fayearthur)
Reporter | ||
Comment 7•12 years ago
|
||
(In reply to Heather Arthur [:harth] from comment #6) > (In reply to Paul Rouget [:paul] from comment #5) > > Heather, do you think we can get that into Firefox 20? > > I wasn't planning on it, because it seemed like a problem with a lot of edge > cases. Which is why I was advocating bug 826982 for 20. I see. > The big edge case is if the file changes on disk or the server and the > changes no longer apply cleanly upon refresh. My thoughts were to get a diff > of changes before the page reloads, if the changes no longer apply, offer an > option to export it as a diff or just revert the files. Indeed, that sounds tricky. Maybe you're right, and bug 826982 is what we should do for now until the styleeditor reboot.
No longer blocks: 816946
Comment 8•12 years ago
|
||
We discussed this in London concluding that when a page is refreshed and there were changes to a stylesheet the user should have the choice to either load the stylesheets with changes or to reload them all. We also said that each stylesheet should have an option to revert.
Updated•11 years ago
|
Assignee: fayearthur → nobody
Comment 9•9 years ago
|
||
Triaging. This has been a P1 for more than 3 years with no significant activity. Returning to the backlog. (Filter on CLIMBING SHOES).
Priority: P1 → --
Comment 10•8 years ago
|
||
Inspector bug triage (filter on CLIMBING SHOES).
Severity: normal → enhancement
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•