Opened 11 years ago

Closed 11 years ago

#6323 closed defect (fixed)

_Templated.html test failing on Safari3.1 (mac and windows)

Reported by: bill Owned by: bill
Priority: high Milestone: 1.2
Component: Dijit Version: 1.0
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by bill)

_AssertFailure: doh._AssertFailure: assertEqual() failed: expected <button widgetid="test1"><span>hello &gt; world</span></button> but got <button widgetid="test1"><span>hello > world</span></button> : assertEqual() failed: expected <button widgetid="test1"><span>hello &gt; world</span></button> but got <button widgetid="test1"><span>hello > world</span></button>
[ Error: assertEqual() failed: expected  hello > world but got  hello > world ]
ERROR IN: simple(t)
FAILED test: simple
_AssertFailure: doh._AssertFailure: assertEqual() failed: expected <button widgetid="test2"><span num="5">hello &gt;&lt;"' world</span></button> but got <button widgetid="test2"><span num="5">hello >&lt;"' world</span></button> : assertEqual() failed: expected <button widgetid="test2"><span num="5">hello &gt;&lt;"' world</span></button> but got <button widgetid="test2"><span num="5">hello >&lt;"' world</span></button>
[ Error: assertEqual() failed: expected  hello ><"' world but got  hello ><"' world ]
ERROR IN: variables(t)

Attachments (1)

innerHTML.html (214 bytes) - added by bill 11 years ago.
test case showing root problem (safari 3.1 has deviant behavior for node.innerHTML)

Download all attachments as: .zip

Change History (5)

comment:1 Changed 11 years ago by bill

Description: modified (diff)

Changed 11 years ago by bill

Attachment: innerHTML.html added

test case showing root problem (safari 3.1 has deviant behavior for node.innerHTML)

comment:2 Changed 11 years ago by bill

Summary: _Templated.html test failing on Safari3.1/mac_Templated.html test failing on Safari3.1 (mac and windows)

This seems like a webkit bug so I filed http://bugs.webkit.org/show_bug.cgi?id=18101

comment:3 Changed 11 years ago by alex

hrm, it doesn't seem like we're gonna get a fix to a browser in time for 1.1. Should this block the release? I'm inclined to say no.

comment:4 Changed 11 years ago by bill

Description: modified (diff)
Resolution: fixed
Status: newclosed

Fixed in [13305]. node.innerHTML may or may not escape > into &gt;... apparently either behavior is correct... so don't use that character in the test.

Note: See TracTickets for help on using tickets.