Just came across this issue. It appears that Firebug v2.0 is causing conflicts with Google Maps (v3). Notable it prevents layers

ReferenceError: rd is not defined

Turns out this is a known issue and has been reported to the Firebug team. (June 11, 2014 at 2:58:19 AM). Issue #7501

It only seems to affect Google Map Layers. The actual map itself will load and correctly resolve a given LatLng object.

It just appears to be a conflict between how Google Map injects the map "layers" (markers, icons, vector, data-layers etc...) and Firebug.

Since June 2004 and it's subsequent first working draft in Jan 2008 HTML5 has, and still is, in flux with a stable recommendation finally slated for the end of 2014, but even as I write HTML5.1 is now being drafted.

One of the many great components of HTML5 was the promise of ubiquitous video and audio content. However due to patent issues, mainly H.264 decoding (licensed through MPEG LA acting as a consortium to these majority stake MPEG Patent holders: Apple, Microsoft, Panasonic, Sony, Dolby, Thomson, and Toshiba (*B)), we've been left with somewhat of a pseudo mash-up of native HTML5 video and Flash Video wrappers unless you wanted to support multiple formats in addition to H.264, namely OGG/Theora.

For a while now Flash has offered a TRULY ubiquitous platform for delivering video and audio content. Gone were the days of having to support .mov for Mac and .wmv for PC

Due to costly patents and the Open Source ethos of projects like Firefox and Opera, these projects have had to, until now, leverage open-source video codecs. Which has led to a slower adoption of video / audio tags in HTML5 across the web.

Spurred on largely by it's Mobile efforts (FirefoxOS) Brendan Eich at Mozilla wrote (Mar 2012) a rather lengthy blog post about their decision to finally, now, adopt H.264.

Instead of building software H.264 decoding directly into the browser they've avoided costly patent fees by relying on H.264 decoding at a hardware level.

What I do know for certain is this: H.264 is absolutely required right now to compete on mobile. I do not believe that we can reject H.264 content in Firefox on Android or in B2G (*A) and survive the shift to mobile.

Losing a battle is a bitter experience. I won’t sugar-coat this pill. But we must swallow it if we are to succeed in our mobile initiatives. Failure on mobile is too likely to consign Mozilla to decline and irrelevance. So I am fully in favor of Andreas’s proposal.

What this means, in short, is that H.264 decoding is now supported in Firefox on a variety of hardware except for Mac OS X due to this bug

• (*A) Boot to Gecko (B2G) is a project with the goal of building a complete, standalone operating system for the Web. It is not a product offering yet, but we are working on transforming it into one.
• (*B) Know Your Rights: H.264, patent licensing, and you

OK, this is a good one. Answers in the comments section.

Q: How do you change the visible number of options in a select box when it drops down, not rendered in the DOM, but when it drops down  ?

I've come to the conclusion you can't because of default parameters specified in the Gecko rendering engine. I know that a <select> element has a "size" attribute which you can access through Javascript with {oSelect}.size or use directly in your HTML with something like <select size="25"></select>, but that changes the number of options visible when the DOM is rendered and not on the drop down event.

For once I think IE and the Trident engine has an advantage over FF and Gecko. IE naturally defaults to display the TOTAL number of <option> items on drop down where as FF is limited to 20, then you have to scroll.

I spent some time looking through the MDC reference manuals, for an interface, some sort of API reference, but the HTML Select Element Interface seems to be limited to the usual foray of methods and properties.

I thought maybe with the introduction of Gecko 1.9 (FF3) and Javascript 1.8 that there might be some interface for changing the default, but wading through documentation there appears not.

So my answer to the question, at the moment is no, but I will be making a suggestion to Mozilla !