Opened 9 years ago

Closed 9 years ago

#11874 closed defect (wontfix)

TabContainer: doesn't render correctly in chrome 6 windows

Reported by: Morphiax Owned by:
Priority: high Milestone: tbd
Component: Dijit Version: 1.5
Keywords: Cc:
Blocked By: Blocking:

Description

Tab container shows a left pointing arrow from the buttonArrows.png sprite instead of the tabs. This is corrected when the page redraws itself, eg. is resized or you move to another browser tab and back again. It does not occur when using the CDN instead of local files. This can be seen with the declarative example from http://docs.dojocampus.org/dijit/layout/TabContainer. You'll need to c and p the whole thing and link to a local version of dojo. This occurs for 1.4.3, 1.5.0 src versions and for both soria and claro themes.

Attachments (2)

tabtest.html (1.4 KB) - added by Morphiax 9 years ago.
Test code
ftab.png (11.5 KB) - added by Morphiax 9 years ago.
See? I'm not mental

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by Morphiax

Attachment: tabtest.html added

Test code

Changed 9 years ago by Morphiax

Attachment: ftab.png added

See? I'm not mental

comment:1 Changed 9 years ago by bill

Component: GeneralDijit
Owner: anonymous deleted
Summary: Tab container doesn't render correctly in chrome 6 windowsTabContainer: doesn't render correctly in chrome 6 windows

Yes, I can see it on http://docs.dojocampus.org/dijit/layout/TabContainer if you switch the "version" drop down to "trunk". That's on Chrome 7 / win. Only w/a clean cache though. Maybe it's that the TabContainer is initializing before the CSS finishes loading?

comment:2 Changed 9 years ago by Morphiax

Ah, yep. Moving the <link rel="stylesheet" type="text/css" href="/dojo-release-1.5.0-src/dijit/themes/claro/claro.css"/> to above the script tags fixes things for me, likewise putting a 5 sec setInterval around the require statements.

comment:3 Changed 9 years ago by bill

Resolution: wontfix
Status: newclosed

OK, good, yes maybe someday we'll have a better solution for this but for now you always need to load the CSS as the very first thing.

Note: See TracTickets for help on using tickets.