Sorry for joining the conversation late.
On Mar 28, 2012, at 1:39 PM, Kenneth Russell wrote:
> On Wed, Mar 28, 2012 at 12:34 PM, Benoit Jacob wrote:
>>
>> 1. In webgl.bufferData implementation, don't call glBufferData, instead just
>> cache the buffer data.
>>
>> 2. In webgl.vertexAttribPoint
2012/4/26 Benjamin Hawkes-Lewis :
>
> On Apr 26, 2012 5:39 PM, "Tab Atkins Jr." wrote:
>>
>> according to the definition of
>> , it appears that authorship information is most appropriate
>> to put there. But sometimes the byline is placed inside the "header"
>> area, which is reasonably marked u
On Apr 26, 2012 5:39 PM, "Tab Atkins Jr." wrote:
>
> according to the definition of
> , it appears that authorship information is most appropriate
> to put there. But sometimes the byline is placed inside the "header"
> area, which is reasonably marked up with a .
Isn't that use case addressed b
I respond below to a number of e-mails regarding audio features in HTML.
The broad picture is that for effects, I recommend we defer to the work
being done at the W3C in the public-audio mailing list.
On Sat, 8 Aug 2009, Chris McCormick wrote:
> On Wed, Jul 08, 2009 at 09:24:42AM -0700, Charles
On Thu, 26 Apr 2012, Paul Adenot wrote:
>
> The played member [1] description of the media element states :
>
> > The played attribute must return a new static normalized TimeRanges
> > object that represents the ranges of the media resource, if any, that
> > the user agent has so far rendered,
The played member [1] description of the media element states :
The played attribute must return a new static normalized TimeRanges
object that represents the ranges of the media resource, if any, that
the user agent has so far rendered, at the time the attribute is
evaluated.
Currently implem
You can specify negative shadow offsets for shadows inside a shape. Is that
not good enough?
david
On Thursday, April 26, 2012, Tyler Larson wrote:
> Shadows can be applied to the outside of anything. This is a great feature
> that is otherwise rather difficult to recreate but why not enable us
On Thu, Apr 26, 2012 at 1:32 AM, Benjamin Hawkes-Lewis
wrote:
> On Apr 25, 2012 9:20 PM, "Andrés Sanhueza" wrote:
>> I see no reason a
>> as in "textual metadata of a section" can't be inside a
>> ("lead of a section"). Could this be considered to be
>> allowed?
>
> Do you have a real example w
Shadows can be applied to the outside of anything. This is a great feature that
is otherwise rather difficult to recreate but why not enable users to be able
to have inner shadows? Things like beveling, embossing and many other stylistic
things that are used in today designs rely on inner shadow
In this version of the canvas spec,
http://www.whatwg.org/specs/web-apps/current-work
which as far as I know of is the new one being worked on, there are two
mentions of letter-spacing but no way to set the letter-spacing.
If you take a look at
http://www.whatwg.org/specs/web-apps/current-work/#
On Fri, 20 Apr 2012 15:19:10 +0200, Julian Reschke
wrote:
I think this is a case where you want to fail early (for some value of
"fail"); so maybe substituting with "?" makes most sense.
Do any servers *expect* the Webkit behavior? If they do so, why don't
they just fix the pages they serv
On Apr 25, 2012 9:20 PM, "Andrés Sanhueza" wrote:
> I see no reason a
> as in "textual metadata of a section" can't be inside a
> ("lead of a section"). Could this be considered to be
> allowed?
Do you have a real example where you think that markup would be useful?
If user agents provide comm
(2012/04/24 15:48), Henri Sivonen wrote:
Does the OS/2 port need it for interfacing with the system APIs? If
the OS/2 port needs it for interfacing with the system APIs, can we
stop exposing the encoding to the Web and can we stop building the
IBM864 encoder/decoder on non-OS/2 platforms? I think
13 matches
Mail list logo
