Closed Bug 451843 Opened 11 years ago Closed 9 years ago

TM: Running Dijit Tree Test with Content JIT enabled causes the TreeView not to appear.

Categories

(Mozilla Labs :: Ubiquity, defect, P1, major)

x86
Windows XP

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: MarcoZ, Unassigned)

References

()

Details

STR:
1. Make sure Content JIT is turned off.
2. Open above URL.

Result: Page appears, including the TreeView.

3. Using about:config, turn javascript.options.jit.content to "true".
4. Close Firefox.
5. Open Firefox, and revisit above URL.

Result: Page appears, but TreeView widget is not displayed. This is visually, not just a11y. The widget is nowhere to be found onscreen.
Flags: blocking1.9.1?
Same is true for the menu test page at Dojo:
http://archive.dojotoolkit.org/dojo-2008-06-25/dojotoolkit/dijit/tests/test_Menu.html

When opening the context menu for either of the "top-left" or "top-right" textboxes, I get the standard Firefox context menu, not the Dojo-generated one.
Blocks: landtm
Blocks: 451602
No longer blocks: landtm
works in

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b1pre) Gecko/20080907020345 Minefield/3.1b1pre

does it work in XP?
The problem got worse recently. With Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080911105329 Minefield/3.1b1pre, when bringing up the Dijit tree test, I now get crashes like:
bp-b81ccb61-8090-11dd-8bf0-001cc45a2ce4. Turning TraceMonkey off makes the crash go away.
Still working here. Does it work if you disable all extensions?
The problematic extension is Ubiquity. Without it, the tree appears if content JIT is enabled, and no crash occurrs.
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P1
Target Milestone: --- → mozilla1.9.1b2
Summary: Running Dijit Tree Test with Content JIT enabled causes the TreeView not to appear. → TM: Running Dijit Tree Test with Content JIT enabled causes the TreeView not to appear.
WFM with TM tip, which is fully merged into MC. Can someone verify?
WFM as well
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
I can still reproduce this bug using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20081207 Shiretoko/3.1b3pre and Ubiquity 0.1.2. If Ubiquity is installed, the trees in the URL above don't get rendered. If Ubiquity is disabled, calling up the URL does work.
Having Ubiquity enabled, but content JIT disabled, will also cause the trees to render properly.

So this is a combination of TraceMonkey content JIT being enabled and Ubiquity being installed and active, for this bug to show up.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee: general → avarma
Component: JavaScript Engine → Ubiquity
Flags: blocking1.9.1+
Product: Core → Mozilla Labs
QA Contact: general → cbeard
Target Milestone: mozilla1.9.1b2 → --
Version: Trunk → unspecified
David, we had a similar bug before. Do you remember the details?
QA Contact: cbeard → ubiquity
Assignee: avarma → ubiquity
Using the latest version of Ubiquity and the latest version of Firefox 3.6, I don't have a problem seeing and using the trees. Given that, and the age of this bug, I'd say something got fixed along the way.

Marking this as RESOLVED WORKSFORME.
Status: REOPENED → RESOLVED
Closed: 11 years ago9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.