|Firebug 1.12 alpha 5||Jan Honza Odvarko||5/3/13 9:02 AM|
This version introduces a Filter for DOM event logging.
Help us decide how to properly implement this feature.
|Re: Firebug 1.12 alpha 5||Sebastian Zartner||5/3/13 3:17 PM|
You missed to discribe another little feature. Like for the other nesting @-rules it is now possible to see @supports rules inside the CSS panel.
Though this currently (Firefox 20.0.1) still needs the about:config preference layout.css.supports-rule.enabled to be set to true.
|Re: Firebug 1.12 alpha 5||Sebastian Zartner||5/3/13 3:53 PM|
Ah, and selection-editing should have been mentioned, too. It's not a new feature, but it's actually very neat and people probably don't know about it.
|unk...@googlegroups.com||5/4/13 1:47 PM||<This message has been deleted.>|
|RE: [firebug] Re: Firebug 1.12 alpha 5||Jan Honza Odvarko||5/7/13 9:32 AM|
Yes, I know I missed some.
What would help me a lot would be a little description of
the new feature + a test page I can use to test and take a
(the test page should always be there anyway).
|Re: [firebug] Re: Firebug 1.12 alpha 5||Sebastian Zartner||5/7/13 1:37 PM|
Each of the features mentioned before has a test page.
And the description of the feature is normally available in the first comment.
To update the release notes I am normally skimming through each fixed feature to summarize what it does.
What else do you need?
|FW: [firebug] Re: Firebug 1.12 alpha 5||Jan Honza Odvarko||5/8/13 5:39 AM|
Well, it isn’t always accurate since the original idea can transform
during the implementation. So, I need to go over the discussion
which is time consuming.
Ideally, when you create the “release-note- wanted” label
put a little description of the new feature (a few sentences)
so, I can use it directly for the blog post.