On Wed, 11 Aug 2010 01:43:01 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
That's a good approach and will reduce the need for breaking
backwards-compatibility. In an xml-based format that need is 0, while
with a text format where the structure is ad-hoc, that need can never be
On 8/10/10, Ian Hickson i...@hixie.ch wrote:
On Wed, 7 Jul 2010, Garrett Smith wrote:
This is about the fourth time I've said it here. Can the person in
charge of writing the slow and buggy ajvascript on the HTML 5 spec
please remove that?
The problem is that that whatwg page causes freezes
On 8/11/10 3:49 AM, Garrett Smith wrote:
I'm running Firefox 3.6.4 on windows 7
Which has a known performance bug with a particular reasonably rare
class of DOM mutations. The only way for the spec to avoid performing
such mutations is to not add the annotation boxes (which is what it will
Ryosuke Niwa:
All popular calendar systems should be supported.
Browser widgets for the datetime types may support more than proleptic
Gregorian, but the spec shouldn’t. ISO 8601 or a subset thereof should be the
interchange format; clients and servers, before and after, may handle it
On Wed, Aug 11, 2010 at 5:04 PM, Anne van Kesteren ann...@opera.com wrote:
On Wed, 11 Aug 2010 01:43:01 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
That's a good approach and will reduce the need for breaking
backwards-compatibility. In an xml-based format that need is 0, while
2010-08-10 21:25 EEST: Tab Atkins Jr.:
On Tue, Aug 10, 2010 at 11:12 AM, Mike Wilcox m...@mikewilcox.net wrote:
This seems like the ideal situation to use a placeholder attribute:
select required=true placeholder=Select an item...
option value=Foo Foo /option
option value=Bar Bar
CC Hixie, question below.
On Tue, 10 Aug 2010 18:39:04 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 8/10/10 4:40 AM, Philip Jägenstedt wrote:
Because the parser can't create a state which the algorithm doesn't
handle. It always first inserts the video element, then the source
elements in
On Wed, 11 Aug 2010 10:30:23 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Aug 11, 2010 at 5:04 PM, Anne van Kesteren ann...@opera.com
wrote:
That is the approach we have for most formats (and APIs) on the web
(CSS, HTML, XMLHttpRequest) and so far a version identifier need
On Wed, Aug 11, 2010 at 2:03 AM, Mikko Rantalainen
mikko.rantalai...@peda.net wrote:
Stuff I don't want to see (combined with @required):
- first option is always special
- empty string as the value is special
- option without a value is special
Do you consider it a problem for input
On Wed, Aug 11, 2010 at 9:31 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Aug 11, 2010 at 2:03 AM, Mikko Rantalainen
mikko.rantalai...@peda.net wrote:
Stuff I don't want to see (combined with @required):
- first option is always special
- empty string as the value is special
- option
On Wed, 11 Aug 2010 13:35:30 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Aug 11, 2010 at 7:31 PM, Anne van Kesteren ann...@opera.com
wrote:
While players are transitioning to WebSRT they will ensure that they do
not break with future versions of the format.
That's
On Wed, 11 Aug 2010 01:43:01 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Tue, Aug 10, 2010 at 7:49 PM, Philip Jägenstedt
phil...@opera.comwrote:
On Tue, 10 Aug 2010 01:34:02 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Tue, Aug 10, 2010 at 12:04 AM, Philip
On Wed, Aug 11, 2010 at 9:49 PM, Anne van Kesteren ann...@opera.com wrote:
On Wed, 11 Aug 2010 13:35:30 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Aug 11, 2010 at 7:31 PM, Anne van Kesteren ann...@opera.com
wrote:
While players are transitioning to WebSRT they will
On Wed, Aug 11, 2010 at 10:30 PM, Philip Jägenstedt phil...@opera.comwrote:
On Wed, 11 Aug 2010 01:43:01 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Tue, Aug 10, 2010 at 7:49 PM, Philip Jägenstedt phil...@opera.com
wrote:
I have checked the parse spec and
On Wed, 11 Aug 2010 15:09:34 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
HTML and CSS have predefined structures within which their languages grow
and are able to grow. WebSRT has newlines to structure the format, which
is clearly not very useful for extensibility. No matter how
On Wed, Aug 11, 2010 at 11:45 PM, Anne van Kesteren ann...@opera.comwrote:
On Wed, 11 Aug 2010 15:09:34 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
HTML and CSS have predefined structures within which their languages grow
and are able to grow. WebSRT has newlines to structure
On 8/11/10, Boris Zbarsky bzbar...@mit.edu wrote:
On 8/11/10 3:49 AM, Garrett Smith wrote:
I'm running Firefox 3.6.4 on windows 7
Which has a known performance bug with a particular reasonably rare
class of DOM mutations. The only way for the spec to avoid performing
such mutations is to
Am 11.08.2010 00:24 schrieb Ian Hickson:
On Mon, 5 Jul 2010, Markus Ernst wrote:
[...]
Example: http://test.rapid.ch/de/haendler-schweiz/iseki.html (This is
under construction.) As a workaround to the height problem, I applied a
script that adjusts the iframe height to the available height in
On Wed, 11 Aug 2010 15:38:32 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Aug 11, 2010 at 10:30 PM, Philip Jägenstedt
phil...@opera.comwrote:
On Wed, 11 Aug 2010 01:43:01 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Tue, Aug 10, 2010 at 7:49 PM, Philip
On 8/11/10 10:31 AM, Garrett Smith wrote:
It would have been more helpful to explain, if you can, the cause of
the slowness in Firefox..
Sure thing. https://bugzilla.mozilla.org/show_bug.cgi?id=481131#c12
(the paragraph starting The time) and
On 8/11/10 11:48 AM, Boris Zbarsky wrote:
javascript:var start = new Date(); function f(n) { for (var k =
n.firstChild; k; k = n.nextSibling) f(k); } f(document); alert(new
Date() - start)
Er, that had a typo. The correct script is:
javascript:var start = new Date(); function f(n) { for (var
On Wed, Aug 11, 2010 at 8:05 AM, Markus Ernst derer...@gmx.ch wrote:
Am 11.08.2010 00:24 schrieb Ian Hickson:
On Mon, 5 Jul 2010, Markus Ernst wrote:
Example: http://test.rapid.ch/de/haendler-schweiz/iseki.html (This is
under construction.) As a workaround to the height problem, I applied a
On Wed, 11 Aug 2010 19:03:28 +0200, Adam Barth w...@adambarth.com wrote:
On Wed, Aug 11, 2010 at 8:05 AM, Markus Ernst derer...@gmx.ch wrote:
A solution at authoring level for cases where the author controls both
pages
would be quite helpful. I think of a meta element in the embedded
On 8/11/2010 06:58, Adam Barth wrote:
On Tue, Aug 10, 2010 at 9:28 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 8/10/10 9:11 PM, Ian Hickson wrote:
Specifically, this means the magic / string is no longer supported
Why? That seemed like a useful feature, and not something
On 8/11/10 2:57 PM, Cris Neckar wrote:
6.1.5
So for example a javascript: URL for a src attribute of an img
element would be evaluated in the context of an empty object as soon
as the attribute is set; it would then be sniffed to determine the
image type and decoded as an image.
Right.
On 8/11/10 5:13 AM, Philip Jägenstedt wrote:
Yes, in the case of the parser inserting source elements that fail one
of the tests (no src, wrong type, wrong media) the algorithm will end up
at step 6.21 waiting. It doesn't matter if all sources are available
when the algorithm is first invoked or
On Mon, 19 Jul 2010, David Flanagan wrote:
The spec describes the transform() method as follows:
The transform(m11, m12, m21, m22, dx, dy) method must multiply the
current transformation matrix with the matrix described by:
m11 m21 dx
m12 m22 dy
0 0 1
The first
On Wed, Aug 11, 2010 at 9:35 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 29 Jul 2010, Gregg Tavares (wrk) wrote:
source-over
glBlendFunc(GL_ONE, GL_ONE_MINUS_SRC_ALPHA);
I tried searching the OpenGL specification for either glBlendFunc or
GL_ONE_MINUS_SRC_ALPHA and couldn't find either.
Ian Hickson wrote:
On Mon, 19 Jul 2010, David Flanagan wrote:
Even changing the argument names to neutral a,b,c,d,dx,dy would be
better than what is there currently.
Done.
Thanks
On Mon, 19 Jul 2010, David Flanagan wrote:
While I'm harping on the transform() method, I'd like to point
On Tue, 20 Jul 2010, Mounir Lamouri wrote:
At the moment, three form elements are barred from constraint
validation: object, fieldset and output. I can understand why object and
fieldset are barred from constraint validation but I think output could
use the constraint validation.
The
On Wed, 21 Jul 2010, Schalk Neethling wrote:
I have been working on getting scrollable tables working across all
browsers. While there exists jQuery plugins that does the job for the
most part, I have to find one that works 100% and works at all in
Chrome. The reason I am putting this to
On Thu, 22 Jul 2010, Brett Zamir wrote:
I would like to see attributes be added to allow iframes to have
independent navigation controls, or rather, to allow a parent document
to have ongoing access to the navigation history of its iframes (say to
be informed of changes to their histories
On Tue, 10 Aug 2010, Charles Pritchard wrote:
I recommend not using canvas for text editing.
I've worked on a substantial amount of code dealing with text editing.
At present, the descent of the current font has been the only
deficiency.
Well, there's also the way it doesn't
On Thu, 22 Jul 2010, Ryan Heise wrote:
[...] For all of the reasons above, I would like to see something like
threads in Javascript. Yes, threads give rise to race conditions and
deadlocks, but this seems to be in line with Javascript's apparent
philosophy of doing very little static
On 8/11/10 4:35 PM, Ian Hickson wrote:
On Mon, 19 Jul 2010, Boris Zbarsky wrote:
I do think the spec could benefit from an example akin to the one in the
CoreGraphics documentation.
I followed your references but I couldn't figure out which example you
meant. What exactly do you think we
2010/8/11 Boris Zbarsky bzbar...@mit.edu:
On 8/10/10 9:11 PM, Ian Hickson wrote:
Specifically, this means the magic / string is no longer supported
Why? That seemed like a useful feature, and not something likely to break
anyone out there
In particular, it allows use cases that are
Re-sending from the correct address.
-- Forwarded message --
From: Boris Zbarsky bzbar...@mit.edu
Date: Wed, Aug 11, 2010 at 12:07 PM
Subject: Re: Javascript: URLs as element attributes
To: Cris Neckar c...@google.com
Cc: wha...@whatwg.org
On 8/11/10 2:57 PM, Cris Neckar wrote:
Resending from the correct address
-- Forwarded message --
From: Cris Neckar c...@google.com
Date: Wed, Aug 11, 2010 at 11:57 AM
Subject: Javascript: URLs as element attributes
To: wha...@whatwg.org
Cc: bzbar...@mit.edu
The HTML5 Spec is somewhat ambiguous on the handling of
On Tue, 10 Aug 2010, Jesse McCarthy wrote:
I consider it highly desirable to have some way to differentiate between
SELECT values explicitly selected by the user and values that were
selected by default and unchanged by the user.
I have a note in the spec to add a feature at some point to
On Thu, Aug 12, 2010 at 1:26 AM, Philip Jägenstedt phil...@opera.comwrote:
On Wed, 11 Aug 2010 15:38:32 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Aug 11, 2010 at 10:30 PM, Philip Jägenstedt phil...@opera.com
wrote:
On Wed, 11 Aug 2010 01:43:01 +0200, Silvia
The first markup example in section 4.6.9 needs updating:
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-time-element
Current Example and text:
=== snip ===
div class=vevent
a class=url
On 8/11/10, Boris Zbarsky bzbar...@mit.edu wrote:
On 8/11/10 11:48 AM, Boris Zbarsky wrote:
javascript:var start = new Date(); function f(n) { for (var k =
n.firstChild; k; k = n.nextSibling) f(k); } f(document); alert(new
Date() - start)
Er, that had a typo. The correct script is:
On Fri, 23 Jul 2010, TAMURA, Kent wrote:
On Sat, Apr 3, 2010 at 06:37, Ian Hickson i...@hixie.ch wrote:
On Sat, 3 Apr 2010, TAMURA, Kent wrote:
I found type=number also had no typeMismatch. If a user wants to
type a negative value, he types '-' first. This state should make
On 8/11/10 9:17 PM, Garrett Smith wrote:
On 8/11/10, Boris Zbarskybzbar...@mit.edu wrote:
On 8/11/10 11:48 AM, Boris Zbarsky wrote:
javascript:var start = new Date(); function f(n) { for (var k =
n.firstChild; k; k = n.nextSibling) f(k); } f(document); alert(new
Date() - start)
Er, that had
On Thu, 22 Jul 2010, Luke Hutchison wrote:
There has been a spate of facebook viruses in the last few months that
have exploited social engineering and the ability to paste arbitrary
javascript into the addressbar of all major browsers to propagate
themselves. Typically these show up as
On Thu, Jul 22, 2010 at 1:46 PM, Adam Barth w...@adambarth.com wrote:
On Thu, Jul 22, 2010 at 1:41 PM, Aryeh Gregor
simetrical+...@gmail.comsimetrical%2b...@gmail.com
wrote:
On Thu, Jul 22, 2010 at 4:32 PM, Luke Hutchison luke.hu...@mit.edu
wrote:
There is no legitimate reason that
46 matches
Mail list logo
