User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; FDM) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2b3) Gecko/20091115 Firefox/3.6b3 preventDefault() failures with firefox alert notification Reproducible: Always Steps to Reproduce: Run attachment. Actual Results: Twice firefox alert notification about no associated protocol. Expected Results: Only one firefox alert notification about no associated protocol, becauce preventDefault() prevents to open link in self.location
Created attachment 415600 [details] modified testcase This bug happens because setting document.getElementById('ifr').contentWindow.location.href to invalid value throws an exception, so preventDefault isn't ever called.
Maybe we shouldn't throw.
Maybe. What does HTML5 say? What do other browsers do?
>> What do other browsers do? Run testcase https://bugzilla.mozilla.org/attachment.cgi?id=415600 Other browsers do not throw.
Yes, my question was about location.href behavior in general, not just on this testcase.
>> my question was about location.href behavior in general https://bugzilla.mozilla.org/show_bug.cgi?id=532602