--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
in the bug you mentioned no longer suffers from the bug.
Therefore, it doesn't appear to be necessary that we should require that
behaviour.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
it in
quirks mode?
As I already said above, neither Opera, Safari or IE8 have the same
behaviour. I tested both quirks and standards mode.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
behaved in
the same way.
What is the use case for wanting a video to be stretched?
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
such annoyances
upon end users if it avoidable; at least not by default.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
...?
There won't be any implementation considered to be the reference
implementation. But the hope is that all implementations will eventually
converge on implementing things in the same way, and that the spec will
match.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Mike Wilson wrote:
Lachlan Hunt wrote:
There will not be, at least in Opera, Firefox or Safari, new
modes added beyond the existing no quirks, limited quirks and
quirks modes.
Do you reckon all, or only some of, these modes will implement the
HTML5 spec? (and differ only in css/rendering
, or determine
that it's not worth addressing.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
to this
requires a copy and paste operation. However, I'm not sure what problem
you're trying to solve. Why would a user want to do this? Why can't
users who want to access their email using a mail client use POP or IMAP?
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
. The problem is getting them to support an import from
clipboard feature.
However, other use cases, like pasting a quote into a word processor
complete with bibliographic information, would need an entirely
different format.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Hi,
The spec defines the semi-transparent content model, but this is no
longer used for any elements. Please remove this from the spec.
http://www.whatwg.org/specs/web-apps/current-work/#transparent-content-models
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
legendA header for the list/legend
ul
liList item/li
liList item/li
liList item/li
/ul
/figure
Since figure is a sectioning root, a heading element could also be used
here and it wouldn't affect the outline. Please add an example of this
use case to the spec.
--
Lachlan
Garrett Smith wrote:
On Wed, Feb 4, 2009 at 2:50 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
As an example of this, consider the element summaries in the HTML 5
Reference, the attribute list has the heading Attributes, but that heading
is not meant to affect the document's outline
style associated with them
(uncommon). So they can be tweaked via CSS. Whether by the author or
overridden by useragent.
I do not understand what you mean here.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
the use case?
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
they are use cases for the
features that you are asking for.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
.
http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#headings-and-sections
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
would make use of the time element
and I couldn't find any use of microformats on that page. Could you
please elaborate on the relevance of that page in regards to this issue?
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
/html-design-principles/#solve-real-problems
[3]
http://esw.w3.org/topic/HTML/DesignPrinciplesReview#head-98fea741b3ace0c8da87029864ec4a5db4b2358e
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Bruce Lawson wrote:
On Thu, 12 Mar 2009 17:05:38 +0530, Lachlan Hunt
lachlan.h...@lachy.id.au wrote:
I think the design principles that are applicable here include Solve
Real Problems [2],
Real problems to be solved:
1) microformats have accessibility problems with abbr; time element
.);
document.fileupload.UploadFileData.focus();
return false;
}
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
. There is also a set
of controls at the top of the specification that does that using
JavaScript, and it also sets a cookie so the choice is remembered.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
that shows the
whole calander for a month or two instead of a drop down.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
comment mean?)
We couldn't use a comment element anyway for backwards compatibility
reasons. IE does some weird stuff when parsing it.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
-11-27
That would allow, for example, user scripts to automatically convert
times in the chat log to local times. It could also be used for styling
purposes, so it can be styled differently to distingish it from the rest
of the line.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http
issues are resolved.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
around the issue, such as using !important
or finding ways to increase the specificity of the latter selector, but
the point is that introducing unnecessary element clashes creates
needless complexities that should be avoided.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http
anyway.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
:
$token:sandbox xmlns:$token=…/$token:sandbox
No, you couldn't use a namespace like that, because then the sandbox
element would not be in the HTML namespace, and thus would not have any
known semantics.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Lachlan Hunt wrote:
Kornel Lesinski wrote:
However, if we're going to introduce token-based sandbox anyway, I
suggest putting token in tag name:
sandbox-$token.../sandbox-$token
where $token is the random part. This avoids oddity of attributes in
closing tag, and is compatible with XML
the last such control that is
inserted.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Enhancements to the DOM API and markup can be
considered later if necessary, such as figuring out how to deal with
drawing an HTMLVideoElement playing a 3D video onto a 2D canvas.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
this extra information
into the existing cache manifest file, or into the HTML with meta and
link elements, rather than creating a whole new manifest file format.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
they don't need may not be worth it.
with no embedded subtitles,
Timed text tracks within WebM (most likely WebSRT) will eventually be
supported.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
of that defaulted to that
wrap=off behaviour. I believe every other mainstream browser I'm aware
of since then wraps by default.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
your proposal correctly?
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
that benefits the subscribers in some
tangible way. Do whatever you do to find a business model that works;
just say no to DRM. It's not needed. The big content industry knows
that, they just won't admit it.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
, you can use AdBlock in Firefox to block the offending
script. Just manually add this URL to your block list.
http://www.whatwg.org/specs/web-apps/current-work/status.js
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
/status.js
The problem is not only with Firefox and it happens I am not only using
Firefox.
Is there a similar blocking feature of Opera that you can suggest ?
Opera includes a Content Blocker feature by default. See Block
Content... in the context menu.
--
Lachlan Hunt - Opera Software
http
about whether the camera
orientation should be relative to the device itself, or relative to
fixed Earth coordinates (North, East, Up), like the existing device
orientation API.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
On 2011-03-14 17:59, Lachlan Hunt wrote:
There are a few issues with the recently added media streaming API.
In addition to what I sent previously, there are some additional use
cases that do not appear to be addressed adequately by the current spec
for streaming media.
In chat clients
to address these use cases using an API based
approach in the future, which will be better than the element based
approach of device, but at this stage it is better to keep things
simple and focus on just audio and video for now.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http
echo or, worse, feedback loops. That
would only be useful if the audio data were being analysed and output,
for example, to an audio spectrum visualisation (like with Mozilla's
experimental audio data API).
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
ondisconnect event in the event model could be handled as
an error event with an appropriate code, though I'm not sure if that's
better or worse than separate event.)
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
in our initial device implementation
and seeking is not possible.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
[2] http://lists.w3.org/Archives/Public/public-webapps/2010OctDec/0169.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
about what the use cases are for knowing if the
camera is either user-view or environment-view. It seems the more
useful information to know is the orientation of the camera. If the
user switches cameras, that could also be handled by firing orientation
events.
Lachlan Hunt wrote
On 2011-03-18 15:14, Olli Pettay wrote:
On 03/18/2011 04:02 PM, Lachlan Hunt wrote:
This is basically what Philip and I were discussing in the other thread
yesterday, where we avoid the unnecessary overhead of creating a magic
URL, and instead just assign the object directly to the src property
(), and enable() and disable() functions have also been
replaced with a single mutable boolean .enabled property.
[1] http://en.wikipedia.org/wiki/Picture-in-picture
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
On 2011-03-18 15:02, Lachlan Hunt wrote:
On 2011-03-18 05:45, Ian Hickson wrote:
On Mon, 24 Jan 2011, Anne van Kesteren wrote:
...
audio.src = blob
(The src content attribute would then be something like
about:objecturl.)
Could you elaborate on this plan?
... we avoid the unnecessary
/C#parse-a-time-component
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
-state
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
, that if the author requests audio,foo, and the
user grants access to audio, then the success callback would be invoked,
despite the unknown option for foo.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
.
No, the implementation should not do that.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
-0
[3] http://images.whatwg.org/sample-details-2.png
[4] http://lachy.id.au/dev/2011/details.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
, though I do prefer
the more elegant display:transparent; approach.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
with using disabled?
input type=checkbox disabled
input type=checkbox disabled checked
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
, but if the controls are readonly, then the user can't
change the value and so why does that matter? Could you clarify the use
case for having a readonly checkbox value submitted?
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
On 2011-04-06 02:56, Lachlan Hunt wrote:
To render this, the following CSS should be applied by the UA stylesheet.
detailssummary:first-of-type {
display: list-item;
margin-left: 1em; /* LTR-specific: use 'margin-right' for rtl elements */
list-style-type: -o-disclosure-closed;
}
details
-image: url(...); }
[open] summary { list-style-image: url(...); }
[1] http://dev.w3.org/csswg/css3-lists/#glyph-counters
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
'. If the spec can make that permissible, then I think
that will be acceptable.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
, as defined in published CSS recommendations, isn’t
bound to any ”::marker”.
It certainly is, in the Lists spec.
Please cite the recommendation by its official name and/or URL.
http://dev.w3.org/csswg/css3-lists/#marker-pseudoelement
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http
to worry about.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
On 2011-04-12 16:18, Lachlan Hunt wrote:
Hi,
We are investigating registerProtocolHandler and have been discussing
the need for a blacklist of protocols to forbid.
Our list currently includes:
* http:
* https:
* ftp:
* file:
Also, blob:
Ancient Netscape scripting schemes. some were
On 2011-04-19 19:33, Ian Hickson wrote:
On Tue, 12 Apr 2011, Lachlan Hunt wrote:
We are investigating registerProtocolHandler and have been discussing
the need for a blacklist of protocols to forbid.
[...]
We'd like to know if we've missed any important schemes that must be
blocked, and we
://www.iana.org/assignments/urn-namespaces/urn-namespaces.xml
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
On 2011-06-15 07:55, Ian Hickson wrote:
On Mon, 28 Mar 2011, Lachlan Hunt wrote:
This should also only allow up to 3 digits representing milliseconds. If
there are 4 or more digits (microseconds or beyond), the spec should
state that the remaining digits should be truncated.
Why?
Because
will only match elements within the div.
http://dev.w3.org/2006/webapi/selectors-api2/#the-scope-pseudo-class
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
On 2011-06-16 00:00, Ian Hickson wrote:
On Wed, 30 Mar 2011, Lachlan Hunt wrote:
The spec states for submission of datetime controls that the value must
be expressed in the UTC time-zone. It's not clear whether this requires
the formatted string to state the timezone as an uppercase Z or
+00
, like
JQuery does, such as allowing selectors to begin with combinators and
creates other unintended side affects. I don't have time to write up a
full explanation now, but most of the rationale is somewhere in the
public-webapps archives.
--
Lachlan Hunt - Opera Software
http://lachy.id.au
parameter of the querySelector* methods
explicitly allows there to be more than one in that context.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Ian Hickson wrote:
On Sat, 12 Mar 2005, Lachlan Hunt wrote:
I realise I may be a little late with this issue, since WF2 seems to be
fairly stable, but never the less I would like to note my objection to
the inclusion of the autocomplete attribute [1].
The autocomplete attribute is already
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
(or equivalent), so
they're not prompted each time.
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
UI when I get
prompted on some sites, but not on others. Hmmm... I wonder if adding
this to my user stylesheet could be useful for giving me some notification.
[autocomplete] { ... }
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com
to be implied by Mozilla and IE. Opera and
OpenSP correctly don't imply the missing head element.
[1] http://www.hixie.ch/tests/adhoc/html/parsing/compat/viewer.html
[2] http://www.is-thought.co.uk/book/sgml-9.htm#Omitting
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover
Anne van Kesteren wrote:
Lachlan Hunt wrote:
HTML5 will most likely stop the pretense of HTML being an SGML
application.
+1.
-1
and the mostly undefined error handling, what about HTML 5 will be so
incompatible with SGML to warrant such a decision?
One example:
http://lists.whatwg.org/htdig.cgi
Olav Junker Kjr wrote:
Lachlan Hunt wrote:
see no problem with defining error handling for broken documents, but
no need to break conformance with SGML in the process. HTML is an
application of SGML, regardless of all the broken implementations and
documents we currently have, and I don't want
Anne van Kesteren wrote:
Lachlan Hunt wrote:
Olav Junker Kjr wrote:
Lachlan Hunt wrote:
Validators should not be non-conformant simply because they only do
their job to validate a document and nothing else. I don't see any
reason why such a statement needs to be included at all.
I don't see
Anne van Kesteren wrote:
Lachlan Hunt wrote:
| Conformance checkers that only perform validation are non-conformant,
So? That doesn't make it a validator.
What is a validator, if it is not a form of conformance checker that
only peforms validation then? Or, the other way around, what
elements within the spec.
ol, ul { display: block }
li { display: list-item; }
p ol, p ul, p li { display: inline }
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
be used in HTML because there are no
namespaces. Whereas, the only reason pol//p can't be used in HTML
is for bugwards compatibility.
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
Henri Sivonen wrote:
On Apr 7, 2005, at 09:58, Lachlan Hunt wrote:
There's no reason why a full conformance checker couldn't be based on
OpenSP.
It would be prudent not to use OpenSP in order to avoid accidentally
allowing SGMLisms that are alien to real-world tag soup.
If I ever get around
] http://www.is-thought.co.uk/book/home.htm
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
being too restrictive.
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
-hyphens -- ensures that the enitire comment remains valid in SGML.
[1] I called it a pseudo comment because it's not really a full comment
in SGML terms, it only looks like one. The real SGML comment is the
full thing including: !-- ... -- -- --
--
Lachlan Hunt
http://lachy.id.au/
http
://meyerweb.com/eric/thoughts/2004/09/15/when-blog-software-attacks/
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
or UTF-16, as described in the XML recommendation.
[1] http://www.whatwg.org/specs/web-apps/current-work/#charset
[2] http://www.w3.org/TR/2004/REC-webarch-20041215/#xml-media-types
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim
Anne van Kesteren wrote:
Lachlan Hunt wrote:
| In HTML (as opposed to XHTML), the title element must not contain
| content other than text and entities; user agents must parse the
| element so that entities are recognised and processed, but all other
| markup is interpreted as literal text.
I
Anne van Kesteren wrote:
Lachlan Hunt wrote:
| In XHTML, the XML declaration should be used for inline character
| encoding information.
|
| Authors should avoid including inline character encoding information.
| Character encoding information should instead be included at the
| transport level
one. The current wording
provides application/xhtml+xml and application/xml as examples only,
which I think is acceptable.
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
are the odds of that? :-)
I've made the spec not restrict the content models per se, just
say this element can contain this category of elements and made sure the
elements are in the right categories.
That seems like the most appropriate way to handle it.
--
Lachlan Hunt
http://lachy.id.au/
http
title=Close up photo of the swing set
area coords=... shape=poly href=tree alt=Old Willow Tree
title=Close up photo of the old, gnarled willow tree
/map
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
Matthew Thomas wrote:
Lachlan Hunt wrote:
...
I don't understand what's wrong with the XML error handling. I think
it's great because errors should be caught and handled during the
authoring process and by the CMS, which XML essentially forces.
http://diveintomark.org/archives/2004/01/14
Anne van Kesteren wrote:
Lachlan Hunt wrote:
Could some of these be improved and included within web apps?
http://lachy.id.au/dev/markup/specs/wclr/
I haven't read it completely, but this sentence sounds incorrect:
# Designates a resource containing user contributed comments. May be
# used
*.
Fair point. Done. I also made it (as you suggested, I think) only the
forms-related parts.
Yes, that looks good.
--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox
Ian Hickson wrote:
On Sat, 16 Apr 2005, Lachlan Hunt wrote:
Perhaps. it's been argued many times before that i is the most suitable
element to use for such purposes; but then again, italics for ship names
is merely a typographical convention and the i element is as meaningless
as span
201 - 300 of 328 matches
Mail list logo
