Opened 11 years ago

Closed 11 years ago

#7528 closed defect (wontfix)

dojoInlineTable renders incorrectly in SeaMonkey

Reported by: inow Owned by:
Priority: high Milestone: tbd
Component: Dijit Version: 1.1.1
Keywords: css seamonkey dojoInlineTable moz-inline-stack Cc:
Blocked By: Blocking:

Description

Using "display: -moz-inline-stack;" in class dojoInlineTable (dijit.css) causes an incorrect rendering in Mozilla SeaMonkey? (tested with SeaMonkey? v1.1.11). Widgets like ComboBox?, Spinner, and TimeTextBox? are rendered as a single horizontal line (about 2px thick) with no content.

I used regular test files (dijit/tests/form/test_TimeTextBox.html, dijit/tests/form/test_Spinner.html) from Dojo 1.1.1.

The only workaround I've found is to set the height attribute in .dojoInlineTable to 1.2em, then the widgets are rendered properly. However this will cause some problems with other widgets that are higher than one line.

Change History (3)

comment:1 Changed 11 years ago by bill

Hmm, we don't really support Seamonkey per se; what version of FF is it based on, BTW?

Having said that, doesn't FF3 support display: inline-block, in which case we should be using that? How does that pan out for SeaMonkey??

comment:2 Changed 11 years ago by inow

Seamonkey is not based on FireFox? directly, it's rather an different packaging of the Gekko engine (and I guess some of the common Mozilla framework). As far as I know, the latest build uses Gekko GECKO181_20080702_RELBRANCH build. See http://www.seamonkey-project.org/releases/seamonkey1.1.11/ Apparently the engine is the same as FireFox? 2.

However, the tests works fine in FF2, so it might be some of the more subtle differences.

The point is that for a framework like Dojo it's not quite easy to tell your users to just use FireFox? 3 while other browsers has some visible problems. I only tried it with SeaMonkey?, but I guess some other branches may have a similar problem.

I think, in general using browser specific hacks (like -moz-inline-stack) is probably not the best approach (although I agree that it's an easy solution), since it may produce different results in different versions of even the same browser.

comment:3 Changed 11 years ago by bill

Resolution: wontfix
Status: newclosed

Hmm, I see.

Yes, well, I know people don't like being told to use a different browser but unfortunately we don't have the bandwidth to support more browsers at this point.

The problem you are talking about has been seen in general, hence the _layoutHack() method. I don't think we can do anything else to fix it, sorry.

Note: See TracTickets for help on using tickets.