Opened 12 years ago
Closed 9 years ago
#12056 closed defect (wontfix)
Opera: layout.module tests fail in runner but pass individually
Reported by: | Katie Vance | Owned by: | Katie Vance |
---|---|---|---|
Priority: | low | Milestone: | future |
Component: | Dijit | Version: | 1.5 |
Keywords: | opera | Cc: | Douglas Hays |
Blocked By: | Blocking: |
Description
AccordionContainer? and nestedStack will pass all tests when run outside of the runner. When run inside the runner I get these failures:
AccordionContainer? runner results:
assertTrue('false') failed with hint: child height > 300 FAILED test: ../../dijit/tests/layout/AccordionContainer.html::animation::select pane #3 with animation 301 ms
nestedStack runner results:
assertEqual() failed:
expected
1
but got
3
with hint: Tab 1 was resized once
FAILED test: ../../dijit/tests/layout/nestedStack.html::after load::TabContainer? 1 content pane 1 visible and resized 0 ms
assertEqual() failed:
expected
1
but got
5
with hint: TabContainer? 2 was resized once
FAILED test: ../../dijit/tests/layout/nestedStack.html::selecting TabContainer? 2::TabContainer? 2 visible and resized 0 ms
ssertEqual() failed:
expected
1
but got
7
with hint: Tab 2 was resized once
assertEqual() failed:
expected
1
but got
3
with hint: Tab 2 was resized once
FAILED test: ../../dijit/tests/layout/nestedStack.html::resize of ContentPane? contents::resize was called on nested layout widgets after tab was made visible 0 ms
Change History (2)
comment:1 Changed 9 years ago by
Priority: | high → low |
---|
comment:2 Changed 9 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Given that Opera is switching to the webkit engine, it doesn't make sense to look at these tickets. We can re-evaluate behavior of dijit on opera after the switch.