The page-up/mousewheel things were already in 10.0a9; the case-insensitive completions <http://code.google.com/p/fbug/issues/detail?id=5493> that can be seen in the screenshot, on the other hand, are new.
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)
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.
> 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.
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?
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!
>>> 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.
<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?
On Sunday, June 3, 2012 4:08:37 PM UTC+1, Jan Honza Odvarko wrote:
> 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
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?
> 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?
