A million little questions

[mcdavis]

1. How does one invoke the Add-Ons Bar? I need to test the skin for #addon-bar

For Fx28 and down, that's Ctrl+/

That doesn't work for me, even in the default theme. Is there an extension that invokes it?

I don't know, not that I know of. There's also menubar > View > Toolbars > Add-on Bar. That's where I saw the shortcut key listed.

[ehume]

And it's not there any more.

And there's this:

Code: Select all

#PanelUI-history.PanelUI-subView {
  border: 2px solid;
  -moz-border-top-colors: #9F9F9F #6B6B6B; /*ThreeDShadow ThreeDDarkShadow;*/
  -moz-border-right-colors: white #EAEAEA; /*ThreeDHighlight ThreeDLightShadow;*/
  -moz-border-bottom-colors: white #EAEAEA; /*ThreeDHighlight ThreeDLightShadow;*/
  -moz-border-left-colors: #9F9F9F #6B6B6B; /*ThreeDShadow ThreeDDarkShadow;*/
}

It makes a border . . but leaves a rim of white, and I can't find out how to enlarge it.

BTW -- the Inspect Context extension will inspect it.

[ehume]

BTW -- the Throbber is gone, isn't it?

[patrickjdempsey]

Yup, that's one of the many things that got lost. Somewhere there is a new extension which restores it though.

[Red_Fat_Lazy_Cat]

Throbber Restored

[mcdavis]

Could someone remind me what [chromemargin] "means", like when is it used and how that has changed for Fx29?

I seem to recall that meant the Firefox button was being shown, but it's hazy.

[patrickjdempsey]

[chromemargin] is on the #main-window element and it tells it whether or not to draw the OS titlebar or borders. If [chromemargin="0,2,2,2"] then it means the titlebar is not drawn by the OS, and Firefox draws it instead. The numbers follow the same convention as other attributes (top, right, bottom, left). The toggle in Customize for Titlebar causes it to be changed. But it could also be used by an extension to remove the borders.

[mcdavis]

[chromemargin] is on the #main-window element and it tells it whether or not to draw the OS titlebar or borders. If [chromemargin="0,2,2,2"] then it means the titlebar is not drawn by the OS, and Firefox draws it instead. The numbers follow the same convention as other attributes (top, right, bottom, left). The toggle in Customize for Titlebar causes it to be changed. But it could also be used by an extension to remove the borders.

Thank you very much. (A slow reply to your quick answer.)

[ehume]

This is happening to me on Macs:



With two different users.

A. What is happening?

B. How do I fix it?

[mcdavis]

This is happening to me on Macs:
A. What is happening?
B. How do I fix it?

I hope to know that by the end of the weekend (for me and for you).

But I can guess it's two things at the same time:

1 - There's a .titlebar-placeholder in the Tabs Toolbar that needs to have Mac-specific rules to give it the proper size and position in the toolbar. It's simply there to occupy space and keep it empty so nothing gets in the way of these system-drawn window control buttons (the ones that OS X draws in every window, there on the left).

2 - The elements #titlebar-buttonbox-container, #titlebar-buttonbox, and all .titlebar-button should probably be hidden, with display: none or visibility: hidden or something, when on OSX. But I don't know details yet.

[mcdavis]

Can someone tell me what is up with DOM Inspector?

I just ran across this and this:

Bug 998492 - The red-exclamation-sign for an "!important" rule isn't displayed anymore
Bug 1018324 - Remove inIFlasher

Does that mean that:

- DOMi is no longer being updated on AMO, but you can still get it by installing Seamonkey and extracting from there?
- You need to use the AMO version of DOM Inspector for Fx27 and down but the one from Seamonkey for Fx28 and up (to get the working indicator of !important in rules)?
- IF so, how do you get the one from Seamonkey? Do you just install Seamonkey, then look in the installation directory to get inspector.xpi?

And that:

- after inIFlasher is removed, DOM Inspector will no longer flash the selected element, even with hardware acceleration disabled?

[ehume]

Try the Inspect Context extension.

[mcdavis]

Try the Inspect Context extension.

Thanks, I did check that out after you mentioned it last weekend I think, it's seemed pretty great. I'll look again.

[mcdavis]

So .. DOM Inspector isn't working in Fx33 Nightlies? I can't click to inspect, and the left-side document tree is empty.

EDIT:

Bug 1023938 - DOM Inspector complains it cannot get Cc["@mozilla.org/inspector/flasher;1"] inIFlasher, rendering it non-functional.
Bug 368608 - Rewrite DOM Inspector's flasher (blink selected element broken)

[patrickjdempsey]

Yeah, something it depended on was removed. They are working on a fix now.