Opened 13 years ago

Closed 13 years ago

Last modified 11 years ago

#9334 closed defect (fixed)

IE8: Wizard close dialog

Reported by: acarli82 Owned by: dante
Priority: high Milestone: 1.4
Component: Dijit Version: 1.3.0
Keywords: Cc:
Blocked By: Blocking:


Hi, if i open a Dialog with href to a page that contain a Wizard object, when click the next step button the Dialog closed automatically.

This problem is present only into internet explorer 8. In this browser is not present:

  • Firefox 3.0.10
  • IE6
  • IE7

Attachments (3)

dialog.html (767 bytes) - added by acarli82 13 years ago.
wizard.html (905 bytes) - added by acarli82 13 years ago.
Wizard_PROBLEM_1.php (3.2 KB) - added by vlad 13 years ago.
vlad_dojo test case, the dialog itself also errors

Download all attachments as: .zip

Change History (21)

comment:1 Changed 13 years ago by Adam Peller

Owner: changed from Adam Peller to dante
Summary: Wizard close dialog in IE8IE8: Wizard close dialog

Is this reproducible with one of our tests? If so, please give specific instructions to reproduce. Thanks.

comment:2 Changed 13 years ago by acarli82

Is not reproducible with test in release 1.3 But if you want i can create a minimal test.


Changed 13 years ago by acarli82

Attachment: dialog.html added

Changed 13 years ago by acarli82

Attachment: wizard.html added

comment:3 Changed 13 years ago by acarli82

I have add a files for test:

  • dialog.html
  • wizard.html

Open dialog.html page, click button for open dialog, then click next button.


comment:4 Changed 13 years ago by acarli82

I have do other test, the problem not is in the Wizard component, but in the button element.

I have add this code at wizard.html page test: <button dojoType="dijit.form.Button" onClick="alert()" id="inviaHelp">Button</button>

When i click button the allert appear but when click the alert the dialog box close.

comment:5 Changed 13 years ago by acarli82

Hi, i have localize the problem in the Button element. All button in IE8 have type "submit" instead of "button".

You can see this with the test: /dojo/dijit/tests/form/test_Button.html

Why? Who change the type of the button? Thanks

comment:6 Changed 13 years ago by acarli82

I have find at this link:

New for Windows Internet Explorer 8 Internet Explorer 8 and later. The default value of this attribute depends on the current document compatibility mode. In IE8 mode, the default value is submit. In other compatibility modes and earlier versions of Internet Explorer, the default value is button.

comment:7 Changed 13 years ago by acarli82

I have resolve with this change at the widget Wizard

_checkButtons: function(){

var sw = this.selectedChildWidget;

var lastStep = sw.isLastChild; this.nextButton.attr("disabled", lastStep); this.nextButton.attr("type", "button"); this._setButtonClass(this.nextButton); if(sw.doneFunction){

console.log(sw.doneFunction); = ""; if(lastStep){ = "none";



#1438 issue here. = "none";

} this.previousButton.attr("disabled", !this.selectedChildWidget.canGoBack); this.previousButton.attr("type", "button"); this._setButtonClass(this.previousButton);


comment:8 Changed 13 years ago by bill

Cc: Douglas Hays added

Ouch, I see that in IE8 on test_Button.html all the dijit.form.Button's have type=submit, even though no type has been specified.

dijit.form.Button sets the default type to button, but the problem is with the parser: it thinks that type has been explicitly set on the srcNodeRef, because node.attributes and node.getAttribute() both indicate so.

Not sure how to deal with this parser problem. (Or rather, this IE8 problem that the parser needs to work around.) Doug, any ideas?

There are some user workarounds, like creating buttons programatically or adding type=button to your markup... but neither is a very good solution.

comment:9 Changed 13 years ago by Douglas Hays

I second "Ouch". This isn't technically an IE8 problem since the default value of BUTTON is supposed to be "submit" and not "button" so this may be a Button widget oversight that we're stuck with for backward-compat reasons.
So adding type=button to user markup may be the correct way to fix this for any BUTTONs (widgets or not) that are embedded within a FORM tag, though IE is being evil for falsifying that "type" was explicitly specified in the markup.

comment:10 Changed 13 years ago by vlad

I also ran into this problem with latest SVN, was going to submit a bug, but I think this is the same as I am seeing. The wizard within dialog disappears (the whole dialog disappears) if the wizard has more than one page. only happens in IE8

I will attach my test case (since I worked on it and it also shows errors out in Dialog itself (but you have to click continue in the IE8 debugger

to get to the wizard).

Most wizards, I think, are used from within a dialog so this is certainly a show stopper for the Wizard control.

None of the supplied tests use it from within a dialog, that's why it passes.

Changed 13 years ago by vlad

Attachment: Wizard_PROBLEM_1.php added

vlad_dojo test case, the dialog itself also errors

comment:11 Changed 13 years ago by dante

Cc: Douglas Hays removed
Component: DojoxDijit
Owner: changed from dante to Douglas Hays
severity: blockermajor

doug, is this something that can be addressed? Seems the problem is in dijit.form.Button right?

comment:12 Changed 13 years ago by bill

As I wrote above, there's no problem in dijit.form.Button, there is an issue with IE8 and the parser that <button> (with no explicit type setting) is parsed as <button type=submit>. But I don't think that's fixable, just need to tell users to stick type=button on all their buttons.

comment:13 Changed 13 years ago by Douglas Hays

Resolution: wontfix
Status: newclosed

There's no way to fix this that I'm aware of. I added a sentence to the Button docs page near the top telling users to add type=button explicitly.

comment:14 Changed 13 years ago by dante

Milestone: tbd1.4
Resolution: wontfix
Status: closedreopened

this still exists in Wizard. there are buttons in the template.

comment:15 Changed 13 years ago by dante

Owner: changed from Douglas Hays to dante
Status: reopenednew

comment:16 Changed 13 years ago by dante

Resolution: fixed
Status: newclosed

(In [20205]) fixes #9334 - making Wizard workable in Dialog by adding type=button to the embedded inline buttons

comment:17 Changed 13 years ago by JP

Adding type="button" resolves this. You will need to add this to the button in the Widget too.

<button dojoType="dijit.form.Button" onClick="handleOnClick()" type="button">Button Text</button>

comment:18 Changed 11 years ago by bill

(In [24185]) Refactor parser to allow attributes (for a single node) to be partly specified in data-dojo-props, and partly specified directly ex: value=123. Uses node.attributes to detect which attributes are specified on a node, or for older versions of IE calls cloneNode(false) followed by some regex's on clone.outerHTML.

Due to lowercase/uppercase issues (ex: tabIndex, onClick), and for type conversion, the code still introspects each widget to get it's attribute metadata. In the future, would like to defer/avoid that in the common case. Fixes #10153, #12423, #12476, #10150, #9823, refs #11490 !strict.

Also fixes the problem on IE8 where a button without type=... defaults to type=submit rather than whatever the widget defines the default as, fixes #10163, refs #9334, #8946.

Future updates will be attached to ticket #12476.

Note: See TracTickets for help on using tickets.