search

Margame / css-x-fire

Automatically exported from code.google.com/p/css-x-fire
0 stars 0 forks source link

IDE does not revert changes if firebug is refreshed #14

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Make a CSS change in Firebug
2. Refresh browser
3. Firebug reverts all CSS

Expected: Since the values are no longer present in the browser, IDE should 
reflect the state of the browser.  
Actual: IDE retains the altered values out of sync with the refreshed state of 
the browser.

or

1. Enter invalid CSS in Firebug
2. Firebug automatically removes the invalid entry

Expected: IDE should stay in sync with Firebug and remove the invalid entry.
Actual: IDE retains the invalid entry.

Windows 7, IntelliJ IDEA 10.0.2, CSS-X-Fire 1.14

Original issue reported on code.google.com by brettm...@gmail.com on 11 Mar 2011 at 5:06

GoogleCodeExporter commented 8 years ago 
I am not sure this is a bug (actually this is why the "trashcan" button exists 
in the IDE plugin). Consider the case when you have a lot of pending changes 
and accidently refresh the browser, or click a link/back/forward. Would you 
accept losing those changes?

The IDE is meant to record changes, but not necessarily to stay in sync with 
the browser. I am all for a fix for the problem described but I'm not sure how 
to deal with it in the best way possible. I know I have users that are against 
the proposed change. Different developers have different workflow...

Would a setting be sufficient, something like "Clear pending changes when 
reloading or leaving page"?

Original comment by ronnie.k...@gmail.com on 11 Mar 2011 at 5:57

GoogleCodeExporter commented 8 years ago 
Fair enough.  Giving the option would be great.  
I do think it should remove invalid entries no matter what though.  I don't see 
a reasonable use case where allowing mistakes to stick around would be 
beneficial.

Original comment by brettm...@gmail.com on 11 Mar 2011 at 6:07

GoogleCodeExporter commented 8 years ago 
Fixed in next relase.

Original comment by ronnie.k...@gmail.com on 20 Mar 2011 at 7:38

GoogleCodeExporter commented 8 years ago 
Thanks for the update!

Original comment by brettm...@gmail.com on 20 Mar 2011 at 8:44