[whatwg] WA1: base

2005-09-02 Thread fantasai
# The href content attribute, if specified, must contain a URI (or IRI). Can the href attribute be empty? # User agents must use the value of the href attribute on the first base # element in the document as the document entity's base URI Current behavior is to use the nearest previous base

[whatwg] WA1: base and href

2005-07-18 Thread fantasai
In HTML 4, the 'href' attribute of the base element is #REQUIRED. Is there a reason why in HTML 5 it is not required? ~fantasai

Re: [whatwg] WA1: base and href

2005-07-18 Thread fantasai
Ian Hickson wrote: On Mon, 18 Jul 2005, fantasai wrote: In HTML 4, the 'href' attribute of the base element is #REQUIRED. Is there a reason why in HTML 5 it is not required? What's the point in making it required? What's the point in making the img element's 'src' attribute required?

Re: [whatwg] WA1: base and href

2005-07-18 Thread Ian Hickson
On Mon, 18 Jul 2005, fantasai wrote: Ian Hickson wrote: On Mon, 18 Jul 2005, fantasai wrote: In HTML 4, the 'href' attribute of the base element is #REQUIRED. Is there a reason why in HTML 5 it is not required? What's the point in making it required? What's the point in making

Re: [whatwg] WA1: base and href

2005-07-18 Thread L. David Baron
On Monday 2005-07-18 08:44 -0400, fantasai wrote: In HTML 4, the 'href' attribute of the base element is #REQUIRED. Is there a reason why in HTML 5 it is not required? base target=foo is pretty common on pages that use frames. Then again, the web apps spec doesn't seem to mention target at

Re: [whatwg] WA1: base and href

2005-07-18 Thread fantasai
L. David Baron wrote: On Monday 2005-07-18 08:44 -0400, fantasai wrote: In HTML 4, the 'href' attribute of the base element is #REQUIRED. Is there a reason why in HTML 5 it is not required? base target=foo is pretty common on pages that use frames. Then again, the web apps spec doesn't