Firebug 1.10a10

[Jan Honza Odvarko]

http://blog.getfirebug.com/2012/06/01/firebug-1-10a10/

Honza

[Simon Lindholm]

Den fredagen den 1:e juni 2012 kl. 18:59:17 UTC+2 skrev Jan Honza Odvarko:

http://blog.getfirebug.com/2012/06/01/firebug-1-10a10/

Honza

The page-up/mousewheel things were already in 10.0a9; the case-insensitive completions that can be seen in the screenshot, on the other hand, are new.

Simon

[Sebastian Zartner]

And you marked issue 5098 and others with fixed-1.10-a10 even when they are unrelated to Firebug.

Sebastian

[cheekybuddha]

Hi,

I still have no red circle with a line through it appear next to a css rule in the css panel to indicate whether I can disable the style or if it is disabled.

The ability to disable/enable works and the style rule goes to grey text when disabled but if I didn't know that it was possible there would be no visual cue to inform me.

Both in FF 13.0 (Win XP)
and Nightly 15.0a1 (2012-05-30) (Ubuntu 12.04)

I guess it's this issue: http://code.google.com/p/fbug/issues/detail?id=5477&can=1&q=label%3Afixed-1.10-a10&colspec=ID%20Type%20Status%20Owner%20Test%20Summary%20Reporter

Cheers,

d

[pd]

Another handy release, woooooohooo! You guys are almost reading my mind. Only this week was I having painful times wanting to get the colour values for some elements but finding they were specified in the unfamiliar rgb() syntax.

Thanks again for the super work.

Long live the 'bug!

On Saturday, June 2, 2012 2:59:17 AM UTC+10, Jan Honza Odvarko wrote:

http://blog.getfirebug.com/2012/06/01/firebug-1-10a10/

Honza

[Sebastian Zartner]

Hi,

I still have no red circle with a line through it appear next to a css rule in the css panel to indicate whether I can disable the style or if it is disabled.

"still" is not correct. This problem occurs since this version.

I guess it's this issue: http://code.google.com/p/fbug/issues/detail?id=5477&can=1&q=label%3Afixed-1.10-a10&colspec=ID%20Type%20Status%20Owner%20Test%20Summary%20Reporter

No, the reason is that the images were replaced by SVG versions, which are not included in the release file.

@Honza:
The build.xml didn't include SVG files for the build process. I changed this right now. Would it be possible to create a new release file for that?

Sebastian

[Sebastian Zartner]

Another handy release, woooooohooo!

Great that you like it!

You guys are almost reading my mind. Only this week was I having painful times wanting to get the colour values for some elements but finding they were specified in the unfamiliar rgb() syntax.

So it seems I was really reading your mind. :-) This was already requested several times and helps a lot.

Though there are still many things on the wish list.

Thanks for testing the freshly baked releases!

Sebastian

[cheekybuddha]

On Sunday, June 3, 2012 10:08:16 AM UTC+1, Sebastian Zartner wrote:

Hi,

I still have no red circle with a line through it appear next to a css rule in the css panel to indicate whether I can disable the style or if it is disabled.

"still" is not correct. This problem occurs since this version.

OK, but I didn't have the graphic in 1.10a9 too!

Keep up the great work,

d

[Sebastian Zartner]

Hi,

I still have no red circle with a line through it appear next to a css rule in the css panel to indicate whether I can disable the style or if it is disabled.

"still" is not correct. This problem occurs since this version.

OK, but I didn't have the graphic in 1.10a9 too!

 

Oh, I see. So then people didn't tell us about that before. Anyway, the fix is very easy. So expect it to be fixed in the next release.

Sebastian

[cheekybuddha]

Oh, I see. So then people didn't tell us about that before.

Sorry, I didn't report it because I thought it was covered by the bug I mentioned!!
 

Anyway, the fix is very easy. So expect it to be fixed in the next release.

That's great - I look forward to it.



Cheers,

d

[Jan Honza Odvarko]

On Jun 2, 7:02 pm, pd <an0n1m...@gmail.com> wrote:
> Another handy release, woooooohooo!
Thanks for the support!

Honza

[Jan Honza Odvarko]

On Jun 3, 11:08 am, Sebastian Zartner

<sebastianzart...@googlemail.com> wrote:
> @Honza:
> The build.xml didn't include SVG files for the build process. I changed
> this right now. Would it be possible to create a new release file for that?

We don't want to have two different releases with the same version
number.
Anyway, I attached a test build to this issue report
http://code.google.com/p/fbug/issues/detail?id=5477

I'll release 1.10a11 next week.
Honza

[cheekybuddha]

Thanks! Test build looks good on initial view - will post back if there are any issues.

Will I need to update manually when 1.10a11 comes out?

I'll release 1.10a11 next week.
Honza

Cheers,

d

[Sebastian Zartner]

On Jun 3, 11:08 am, Sebastian Zartner
<sebastianzart...@googlemail.com> wrote:
> @Honza:
> The build.xml didn't include SVG files for the build process. I changed
> this right now. Would it be possible to create a new release file for that?
We don't want to have two different releases with the same version
number.
Anyway, I attached a test build to this issue report
http://code.google.com/p/fbug/issues/detail?id=5477

You should have attached the build here in this thread, Honza. As I said before it isn't related to issue 5477.

Thanks! Test build looks good on initial view - will post back if there are any issues.

The only other symbols that were replaced by SVG icons so far are the ones in the console for errors, warnings and info messages.
 

Will I need to update manually when 1.10a11 comes out?

It should normally update automatically.

Sebastian