Bug with FirePicker and FireBug #28

Closed
rifton007 opened this Issue Oct 21, 2012 · 4 comments

Comments

Projects
None yet
3 participants

Hello,

I have no problem with FireBug.
But when I install FirePicker. Can not edit or add CSS rules.
Also "autocompletion" no longer works.

I disable all other modules.
Remove and install FireBug and FirePicker.

Firebug 1.10.4
FirePicker 1.4.2
16.0.1 FireFox
Windows 7 (6.1 SP1) 64x

Thank you for your help.
And sorry for my english, I'm french.

Owner

thedarkone commented Oct 21, 2012

Hello,

what you are describing looks to be a repeat of issue #23. Can you try repeating the steps suggested by @SebastianZ in that ticket?

A big thank you, it works.
I create a new profile FireFox.

https://getfirebug.com/wiki/index.php/FAQ#Installing_in_a_clean_profile

thedarkone closed this Oct 21, 2012

I can see such problems when the accessibility enhancements are enabled. This can be done via Firebug Menu > Options > Enable Accessibility Enhancements.

Test case:

  1. Open Firebug on https://getfirebug.com/
  2. Switch to the HTML panel and there to the Style side panel
  3. Check the option Enable Accessibility Enhancements
  4. Inside the Style side panel click the value (#333333) of the color property inside the body rule
    => The inline editor opens and shows the value of the color inside of it. (OK)
  5. Press Escape
  6. Click the value again

=> The inline editor is opened, but the value is not shown inside of it. (BUG)

Similar things happen when you try to add a new property or edit another property. Sometimes you'll even see a previously entered property name in the value field. So it looks like the inline editors get mixed up.

Sebastian

@thedarkone thedarkone added a commit that referenced this issue Nov 14, 2012

@thedarkone thedarkone Fix an incompatibility with the FB's Accessibility Enhancements optio…
…n. Fix #23, #28.

Big thanks to @SebastianZ for tracking this down!
26b5941

Tested using FF 16.0.2 + FB 1.10.6 and it works fine for me. Thanks!

Big thanks to @SebastianZ for tracking this down!

You're welcome.

Sebastian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment