Opened 13 years ago

Closed 12 years ago

#9074 closed defect (fixed)

dijit.Editor and TabContainer do not init properly when given inside of a widget template

Reported by: frietsch Owned by: liucougar
Priority: high Milestone: 1.4
Component: Editor Version: 1.3.0
Keywords: editor tabcontainer template Cc:
Blocked By: Blocking:


I've been trying to extend the dijit.Editor with a source view, i.e. a textarea that should allow editing plain HTML if the user needs to insert things that are not supported by dijit.Editor. My plan was to use a TabContainer?, with the editor on one tab and the source view on another one. Unfortunately, this approach only seems to work if I include all the markup in the main document. Putting exactly the same markup into a template and creating a new combined widget results in rendering problems.

See the attached example: The first tabs/editor block (template) renders two tab buttons *below* each other and no editor at all. The second tab/editor block (main document) seems OK. I've seen this bug in IE8 and FF3. Strangely, the first tab/editor block sometimes seems to come up when I use the browser's "Find Text" feature with "h", for example.

Attachments (3)

BugDemo.html (358 bytes) - added by frietsch 13 years ago.
tabs.html (1.2 KB) - added by frietsch 13 years ago.
Result.png (11.9 KB) - added by frietsch 13 years ago.
Rendering in FF3

Download all attachments as: .zip

Change History (5)

Changed 13 years ago by frietsch

Attachment: BugDemo.html added


Changed 13 years ago by frietsch

Attachment: tabs.html added


Changed 13 years ago by frietsch

Attachment: Result.png added

Rendering in FF3

comment:1 Changed 13 years ago by frietsch

Any ideas? I think it's not really a DOM creation bug, but a display bug. Otherwise, things couldn't sometimes improve when I search for text, forcing the browser to redraw the page. Maybe it is possible to force it to redraw manually or something?

comment:2 Changed 12 years ago by bill

Milestone: tbd1.4
Resolution: fixed
Status: newclosed

This has been fixed with all the widgetsInTemplate refactoring for 1.4, in #9348.

Note: See TracTickets for help on using tickets.