Re: [whatwg] A plea to Hixie to adopt , and main element parsing behaviour
Hi all, How have you been? It's nice that we all are still alive. Previously I proposed making element a sectioning element for a better and clearer document outline. In the proposal, I gave an example to demonstrate the HTML codes. ( http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Oct/0154.html) And today I saw a HTML5 template called HTML5 Bones (http://html5bones.com/). In the index.html of the template, I noticed that is placed within . I then realized that the template is right, and the example in my above mentioned proposal is wrong. Complementary Content belongs to Main Content, so it should be placed within Main Content. If you place Complementary Content outside of Main Content, you are actually indicating that they have no association. Thank the template for reminding me of this important thing. So please allow me to correct my example. The ideal HTML code and document outline should be as follows: blablabla Branding Navigation blablabla Search blablabla Main Content Welcome blablabla Brief Intro blablabla Complementary Content Latest News blablabla Recent Comments blablabla blablabla 1. Branding 1. Navigation 2. Search 3. Main Content 1. Welcome 2. Brief Intro 3. Complementary Content 1. Latest News 2. Recent Comments Besides, after some reconsiderations, I would still propose that can be used multiple times in a document so that we have a reasonable element to wrap the main content of a blog post. And yes, the document outline will become *more detailed* because of being sectioning element. That will be okay imo. Another reason for this proposal is that because the main content of a document has its corresponding element, it's unfair and makes no sense that the main content of a blog post doesn't. The following is an example. blablabla Main Content blablabla To sum up, the proposals are: 1. Making a sectioning element for a better and clearer document outline. If unfortunately it were not accepted, personally I guess I will continue to use at least it yields an ideal document outline. 2. Making being usable multiple times in a document, so we also have a reasonable element to wrap the main content of a blog post. Any suggestion or advise will be greatly appreciated. Thanks. Regards, Ian Yang
Re: [whatwg] feedback
On Thu, 20 Dec 2012, Jer Noble wrote: > On Dec 17, 2012, at 4:01 PM, Ian Hickson wrote: > > > > Should we add a preciseSeek() method with two arguments that does a > > seek using the given rational time? > > This method would be more useful if there were a way to retrieve the > media's time scale. Otherwise, the script would have to pick an > arbitrary scale value, or provide the correct media scale through other > means (such as querying the server hosting the media). Additionally, > authors like Rob are going to want to retrieve this precise > representation of the currentTime. If rational time values were > encapsulated into their own interface, a "preciseCurrentTime" (or > similar) read-write attribute could be used instead. Ok. I assume this is something you (Apple) are interested in implementing; is this something any other browser vendors want to support? If so, I'll be happy to add something along these lines. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] what use-case is there for the name-attribute on a fieldset?
On Fri, Dec 21, 2012 at 12:39 PM, Evert Van dansen wrote: > I am sorry, perhaps I misunderstand, but I do not see what the advantage is > over using "regular" hooks (like id) in this case? Surely adding the > name-attribute must have been a decision based on something specific? Oh, the reason was likely that it was already widely supported, despite not being mentioned in HTML4. -- http://annevankesteren.nl/
[whatwg] what use-case is there for the name-attribute on a fieldset?
Hello, Recently I noticed that HTML5 allows the name-attribute on a fieldset. This was not the case in HTML4.0.1. I did some tests and noticed that this name is *not* part of the POSTed data when submitting a form? So I was wondering when and for what purpose this name-attribute should or could be used? Thanks.
