(In reply to Jeff Griffiths (:canuckistani) (:⚡︎) from comment #14) big messages through the message manager are not cheap, so it's probably not good to send all computed styles for every item and every supported CSS property if we want native menu look, we need to take care of the default styles which are different between and figure out if we want native menupopup look, or native dropdown look There are some non-straightforward issues to solve, such as: I don't know where to find the exhaustive list) Not every CSS property is supported in them, but several are, such as: color, background-color, margins, paddings, font, font-size, font-weight, text-decoration, etc. However, the rendering is not equivalent because the CSS styles that affect the rendering of these elements are not passed to the parent. In bug 897060 we implemented support for displaying the dropdowns from widgets in the parent, by opening a menupopup filled with menuitems equivalent to the content from the children elements from the widget.
0 Comments
Leave a Reply. |