Re: [whatwg] The issue of interoperability of the element

2007-06-26 Thread Spartanicus
erim build did not support . -- Spartanicus

Re: [whatwg] The issue of interoperability of the element

2007-06-26 Thread Spartanicus
s, including commercial realities. But I don't accept that idealistic advocacy regarding encoding format support for the element is pointless in the situation in which we are today where the market leaders haven't yet decided what they are going to do. -- Spartanicus

Re: [whatwg] The issue of interoperability of the element

2007-06-26 Thread Spartanicus
ste of electronic bits. Agreed with regard to the criticism of Apple. Couldn't disagree more with regard to fighting for open and free web content formats. -- Spartanicus

Re: [whatwg] The issue of interoperability of the element

2007-06-25 Thread Spartanicus
la support a common codec, and if that codec roughly meets the quality vs bandwidth requirements of content providers then imo there's a high probability that this format will be used to create future audio and video web content. Anyone know if Microsoft and Mozilla have expressed their wishes and intentions? -- Spartanicus

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Spartanicus
ng it? And didn't MS stop including their "Java" in recent OSs after they lost the court case with Sun? -- Spartanicus

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Spartanicus
e considered too much of a hindrance when Flash "simply works". >Where there's a will, there's a way. We have to do what is right, not >what is politically acceptable. Frustrated as I am with the current state of affairs, I don't see any point in taking a principal stance if it will result in being ignored. -- Spartanicus

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Spartanicus
gt;Keeping it, or changing to wording will not >change the behavior of Microsoft and Apple, but will only ensure that HTML5 >will never become fully supported in the major browsers. Support for the element without a common codec may well become fully supported, but pointless. Consequently and with regret I favour removing from the spec. -- Spartanicus

Re: [whatwg] Target Attribute Values

2007-04-28 Thread Spartanicus
" is imo much too strongly put, more so because the user has deliberately enabled the config setting that prevents this. -- Spartanicus

Re: [whatwg] Target Attribute Values

2007-04-28 Thread Spartanicus
ufacturers can ignore such, the only effect is that they can't claim to be spec conforming. User demand for such UI features expressed to the manufacturer is one way to get such features implemented. Other web specs have seen fit to add their weight to get UI features implemented. -- Spartanicus

Re: [whatwg] Target Attribute Values

2007-04-28 Thread Spartanicus
windows despite it having been pointed out that doing so is bad practice. The most common reasons given are: 1) I like [often off-site] links opening in a new window, others will too. 2) When moving to another site, not opening a new window would cause my site to disappear (sometimes accompanied with the argument that this would confuse people). -- Spartanicus

Re: [whatwg] Target Attribute Values

2007-04-26 Thread Spartanicus
g just that. Would perhaps a spec conformance requirement that browsers should offer users a config option to opt out of windows being opened via target values be an alternative? It could avoid the seemingly unwin'able argument with authors who insist on doing this, and give users the final say Mozilla already offers such an opt out afaik. -- Spartanicus

Re: [whatwg] Section nesting menu and an old HTML 3 friend LH

2007-04-03 Thread Spartanicus
ar Nissan Jaguar Bicycle Road Bikes Raleigh Scott Mountain Bikes Specialized -- Spartanicus

Re: [whatwg] Section nesting menu and an old HTML 3 friend LH

2007-03-30 Thread Spartanicus
oblem to solve here, or that a case can be made where list headings would offer any potential benefit over using a element (leaving aside the useless "it isn't a paragraph" argument). -- Spartanicus

Re: [whatwg] on codecs in a 'video' tag.

2007-03-27 Thread Spartanicus
as the baseline codec may require people who wish to author content using that format to pay for the privilege. This is currently the case for mp3 [1]. Although afaik this isn't currently the case for non commercial usage, the rights holders can change that at any given moment. [1] http://www.mp3licensing.com/help/index.html#4 -- Spartanicus

Re: [whatwg] , Flash, & IE7

2007-03-21 Thread Spartanicus
s default restrictions appear to be most strict when loading a file from the local file system, more relaxed when loading from a domain that falls under IE's "Local intranet" group, and most relaxed for domains in its "Internet" group. I was expecting the opposite and had te

Re: [whatwg] element feedback

2007-03-21 Thread Spartanicus
lying on JS for anything essential at least from a specification angle. [1] CSS3 generated content WD enables blurring the distinction between content and styling by enabling fall back content: http://www.w3.org/TR/2003/WD-css3-content-20030514/#inserting3 Example: content: url(danger.png), "Da

Re: [whatwg] element feedback

2007-03-21 Thread Spartanicus
sing conditional comments authors can still use the advantages of the object element whilst feeding IE an element instead. -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] element proposal

2007-03-16 Thread Spartanicus
ere to works almost nowhere. Transcoding from one lossy format that is used on the web to another results in a significant reduction in quality compared to a non lossy source to lossy end format encoding, so you shouldn't make quality vs file size judgements based on that type of transcoding. -- Spar

Re: [whatwg] Clarify how to indicate document hierarchy

2007-03-15 Thread Spartanicus
Spartanicus <[EMAIL PROTECTED]> wrote: >I'd much rather see different authors writing their own best authoring >guidelines using their own argumentation and have these compete for >adoption amongst peers. Having said that I felt obliged to write something on the subject mys

Re: [whatwg] element proposal

2007-03-01 Thread Spartanicus
there was a way to ensure that video can play in it's native size, whilst at the same time knowing in advance what room to reserve in the flow for the media and any player chrome. -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] Clarify how to indicate document hierarchy

2007-02-12 Thread Spartanicus
ve a page on the WhatWG site that links to such authoring guidelines accompanied with a warning that they are not necessarily endorsed by the group. The spec itself could then refer people looking for more verbose usage guidelines to that page. -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] Clarify how to indicate document hierarchy

2007-02-12 Thread Spartanicus
should get involved with. >It should indicate both IMHO, and in many places both the >HTML4 specification and the WHATWG drafts do just that. I see no guidance of the type you requested in the HTML4 spec. Whilst I can understand your desire for this type of advocacy, a language specification is IMO

Re: [whatwg] Clarify how to indicate document hierarchy

2007-02-12 Thread Spartanicus
u noted, there are differing views on what constitutes best authoring practice is another argument that this is not something a specification should get involved with. -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] contenteditable, and

2007-01-12 Thread Spartanicus
false semantics (one of the least significant issues IMO). Afaics this is off topic for this list, so I'm not going to add further to this thread spin off. -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] several messages about XML syntax and HTML5

2006-12-22 Thread Spartanicus
limited cases where I >don't see that this applies. So "should" is just your narrow viewed opinion >which is no more "correct" than my broader viewed opinion. "should" (in lower case) should not be read as per RFC 2119, that should be (I'm a bad boy) reserved to the upper case usage of the word. I'm going back to lurk mode, as I've strayed well beyond the purpose of this list (sorry). -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] several messages about XML syntax and HTML5

2006-12-21 Thread Spartanicus
2F%2Fwww.yahoo.com http://validator.w3.org/check?uri=http%3A%2F%2Fwww.tech.msn.com Should give some indication. (I had to cheat slightly with MSN, the sneaky boys made the home page on msn.com validate to throw people off, but as I suspected the document at the first link from msn.com I tried failed val

Re: [whatwg] HTML syntax: comments before doctype and doctypesniffing

2006-12-03 Thread Spartanicus
upport for the child selector to "standards mode". These sites extensively used the child selector hack to apply fallback CSS for IE and advanced CSS for proper browsers, advanced CSS that by that time I knew IE7 was unlikely to support (like generated content or CSS tables). -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] HTML syntax: comments before doctype and doctype sniffing

2006-12-03 Thread Spartanicus
would you want to deny an author who fully understands the issues from doing this? -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] element comments

2006-11-04 Thread Spartanicus
e problem is that all cases when people omit the alt attribute >because they don't care will end up with mangled meaning. I don't see that as changing anything. Documents containing content images without alt content are broken regarding this aspect, and they will remain so if without an alt attribute is considered equal to elements with alt="". -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] element comments

2006-11-04 Thread Spartanicus
ossible, nor do I believe that allowing width & height attributes could create a precedent. The question should be if maintaining these serves a valid useful purpose. -- Spartanicus (email whitelist in use, non list-server mail will not be seen)

Re: [whatwg] element comments

2006-11-04 Thread Spartanicus
ople be ok with that? Definitely on the integer value only, allowing percentage values makes no sense to me. In some cases I have used just one attribute http://homepage.ntlworld.ie/spartanicus/fit_image_in_column2.htm , but on examination this does not only have no benefit, it needlessly causes th