13859 2011-08-22 08:02:57 +0000 It seems href IDL attribute on base element doesn't reflect content attribute when there is more than one base element with "href". 2011-10-25 02:01:29 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other CLOSED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-base-element P3 normal --- 1 contributor ian bzbarsky csf178 ian kennyluck mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 55565 0 contributor 2011-08-22 08:02:57 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#the-base-element Complete: http://www.whatwg.org/c#the-base-element Comment: It seems href IDL attribute on base element doesn't reflect content attribute when there is more than one base element with "href". Posted from: 114.80.133.8 by csf178@163.com User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.41 Safari/535.1 55566 1 csf178 2011-08-22 08:12:23 +0000 Consider the following html: <!DOCTYPE html> <html xmlns=" http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=GB2312" /> <base id="a" href=" http://www.baidu.com" /> <base id="b" href=" http://www.google.com" /> <title></title> </head> <body> <script type="text/javascript"> alert([document.getElementById("a").href,document.getElementById("b").href]); </script> </body> </html> According to the standard "The href IDL attribute, on getting, must return the page's document base URL" a.href and b.href should return the same value " http://www.baidu.com". But this behavior is different from most implementations'. 55573 2 Ms2ger 2011-08-22 10:12:39 +0000 From code inspection, webkit reflects, and Gecko returns the content attribute, if it exists, and the page's document base URL otherwise. 57818 3 ian 2011-10-04 23:40:23 +0000 Opera seems to just reflect as well. How important is Gecko's behaviour when there's no attribute? Anyone know what IE does? 57845 4 Ms2ger 2011-10-05 13:04:11 +0000 http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1180 I get log: http://software.hixie.ch/utilities/js/live-dom-viewer/foo log: http://software.hixie.ch/utilities/js/live-dom-viewer/bar log: with IE9 (and the same without a doctype), so seems like they reflect as well. Ignore what I said before about Gecko, I don't actually understand what the code does. See <https://bugzilla.mozilla.org/show_bug.cgi?id=600809> for its behaviour, though. 57846 5 bzbarsky 2011-10-05 14:27:25 +0000 > I don't actually understand what the code does. Gecko's code for .href on a <base> attribute is as follows: 1) Try to create a valid URI using the document's current URI as the base URI and the value of the attribute as the uri reference. 2) If this succeeeds, return the result. 3) If not, return the value of the attribute. 58028 6 csf178 2011-10-11 03:25:25 +0000 (In reply to comment #5) > > I don't actually understand what the code does. > > Gecko's code for .href on a <base> attribute is as follows: > > 1) Try to create a valid URI using the document's current URI as the base URI > and the value of the attribute as the uri reference. > 2) If this succeeeds, return the result. > 3) If not, return the value of the attribute. I tried the HTML above in Firefox 7.0 and the two base element returns different value when get IDL attribute href. It looks conflict with Boris' comment? 58062 7 bzbarsky 2011-10-11 16:45:04 +0000 > It looks conflict with Boris' comment? Only if you misunderstood my comment. Step 1 from my comment would lead to different values for the HTML from comment 1, if that's what you were testing on. 58114 8 csf178 2011-10-12 10:46:58 +0000 (In reply to comment #7) > > It looks conflict with Boris' comment? > > Only if you misunderstood my comment. Step 1 from my comment would lead to > different values for the HTML from comment 1, if that's what you were testing > on. Ah. Sorry, I misunderstand step 1. It should lead to different values. I tried IE8、Chrome and Firefox. I set a relative URL to href and all the three browsers returned the resolved URL on getting. 58763 9 ian 2011-10-24 17:44:44 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Ok, I went with just reflecting. This doesn't match Gecko in the case where the attribute is absent, but that doesn't seem necessary for compat since the other browsers don't do it. 58764 10 contributor 2011-10-24 17:45:16 +0000 Checked in as WHATWG revision r6734. Check-in comment: <base>.href reflects, apparently. http://html5.org/tools/web-apps-tracker?from=6733&to=6734