Nov 14, 2008, в 2:30 AM, Ian Hickson написал(а):
I believe that the idea that the API for shared and dedicated workers
should be the same is misguided. The spec used to make the two cases
identical. The result was confusion, and the dedicated case was much
more
complex than necessary.
Hi,
I don't know if the question has already been posted...
Would it be possible to have media attribute in the SCRIPT element?
Addmitted vaues would be the same of STYLE element (all, screen, print,
handheld ...)
Personally, I'd really love this feature.
Thank you
Kind regards
Filippo
--
On Fri, Nov 14, 2008 at 06:09, Nils Dagsson Moskopp
[EMAIL PROTECTED] wrote:
The small element represents small print [...]
The b element represents a span of text to be stylistically offset from
the normal prose without conveying any extra importance [...]
Both definitions seems rather
Nov 14, 2008, в 3:59 AM, Ian Hickson написал(а):
For the sake of completeness, a connect/startConversation method on a
worker really should automatically open the receiving port - this is
what examples posted so far implied, and it would cause a lot of
aggravation if it didn't. I know I'm
Nov 14, 2008, в 7:37 AM, Jonas Sicking написал(а):
Feel free to try our implementation of a subset of the spec ;)
I did not say that there was anything wrong with Mozilla's
implementation! What I said was that it was very different from the
current spec, at least in spirit.
In fact,
Hi,
Would it be possible to have media attribute in the SCRIPT element?
Addmitted vaues would be the same of STYLE element (all, screen, print,
handheld ...)
Thank you
Kind regards
Filippo
On Fri, Nov 14, 2008 at 9:00 AM, Jonas Sicking [EMAIL PROTECTED] wrote:
Oh?! Then I understand even less what the use case is. This is something
that doesn't exist for script and i've never heard anyone ask for it
(granted, that is not proof that no one wants it).
a script can figure out where
Ian Hickson wrote:
On Fri, 17 Oct 2008, Mike Wilson wrote:
but for more decoupled systems you may want to specify a
HTML snippet per object type or similar - and then apply
recursive view rendering on an object graph.
I agree, but it seems that having the hidden inputs be inside
the
Nov 14, 2008, в 10:00 AM, Jonas Sicking написал(а):
What are the use cases? Also note that we can't use it with shared
workers since they can be connected to several pages from
different uris.
It returns the script's URL, not the page's.
Oh?! Then I understand even less what the use case
The small element represents small print [...]
The b element represents a span of text to be stylistically offset from
the normal prose without conveying any extra importance [...]
Both definitions seems rather presentational (contrasting, for example,
the new semantic definition for the i
Dne Fri, 14 Nov 2008 14:40:20 +0100 Pentasis [EMAIL PROTECTED]
napsal/-a:
I agree with the original poster on this.
1) Just because it makes sense to a human (it doesn't to me), does not
mean it makes sense to a machine.
2) When using small on different text-nodes throughout the document,
On Fri, Nov 14, 2008 at 7:40 AM, Pentasis [EMAIL PROTECTED] wrote:
The small element represents small print [...]
The b element represents a span of text to be stylistically offset from
the normal prose without conveying any extra importance [...]
Both definitions seems rather
Of course not. You're not intended to. What you *do* get, though, is that
this is a word which is *intentionally* stylistically offset from the rest
of the text. This conveys semantic meaning to a human - it means that the
word is special or being used in a particular context. b and i don't
On Fri, Nov 14, 2008 at 9:38 AM, Pentasis [EMAIL PROTECTED] wrote:
Of course not. You're not intended to. What you *do* get, though, is that
this is a word which is *intentionally* stylistically offset from the rest
of the text. This conveys semantic meaning to a human - it means that the
On Thu, Nov 13, 2008 at 9:12 PM, Pierre-Olivier Latour [EMAIL PROTECTED]wrote:
In any case, if this attribute really needs to be present, we should rename
it at the minimum (picking a term from the professional video world
requires taking the constraints that come with it), maybe displayRatio
Ian,
Thanks for taking the time to read and understand all the feedback.
Although this is not my most preferred design for the API, I can live
with it. I'm happy that we removed startConversation(). I think that
was just extra complexity on top of an already large API.
As for putting forward
On Friday 2008-11-14 11:37 +0100, Filippo Levizzani wrote:
Would it be possible to have media attribute in the SCRIPT element?
Addmitted vaues would be the same of STYLE element (all, screen, print,
handheld ...)
I'm not quite sure how this would work, since there are two things
that seem
If we wish to communicate that level of semantics, yes. It may not be
useful to us. If you *really* need some metadata/semantics, @class probably
can't convey it with enough granularity. Check out the big discussion from
a few months ago about ccRel and RDFa.
Not yet maybe, but we could
On Fri, Nov 14, 2008 at 10:44 AM, Pentasis [EMAIL PROTECTED] wrote:
If we wish to communicate that level of semantics, yes. It may not be
useful to us. If you *really* need some metadata/semantics, @class probably
can't convey it with enough granularity. Check out the big discussion from
Nov 14, 2008, в 8:50 AM, Jonas Sicking написал(а):
To fix all this I propose that if a port has been started, we don't
allow it to be passed to postMessage. If that is done an exception is
thrown.
Could you please explain how this scenario is affected by the port
being started? Messages
On Thu, Nov 13, 2008 at 10:17 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Aaron Boodman wrote:
On Thu, Nov 13, 2008 at 8:45 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 13 Nov 2008, Jonas Sicking wrote:
Actually, i think we should remove the location accessor as well. I
can't think of a
On Friday 2008-11-14 18:53 +0100, Filippo Levizzani wrote:
* whether a media attribute is true can change over time
but the same applies to style element , I guess
Yes, but styles can be applied and unapplied easily.
This seems to imply that we'd have to go un-execute a script, or
that
Could a list admin please contact me off-list regarding strange bounce
errors? I've tried contacting an admin through the list admin email
twice and have received no responses.
Thanks
Aaron
Alexey Proskuryakov wrote:
Nov 14, 2008, в 8:50 AM, Jonas Sicking написал(а):
To fix all this I propose that if a port has been started, we don't
allow it to be passed to postMessage. If that is done an exception is
thrown.
Could you please explain how this scenario is affected by the port
Alexey Proskuryakov wrote:
Nov 14, 2008, в 10:00 AM, Jonas Sicking написал(а):
What are the use cases? Also note that we can't use it with shared
workers since they can be connected to several pages from different
uris.
It returns the script's URL, not the page's.
Oh?! Then I understand
Nov 14, 2008, в 11:31 PM, Jonas Sicking написал(а):
Could you please explain how this scenario is affected by the port
being started? Messages are queued in closed ports until those are
started, so I think that it applies word to word to closed ports.
Where the messages are queued are an
On Fri, 14 Nov 2008, Filippo Levizzani wrote:
Would it be possible to have media attribute in the SCRIPT element?
Addmitted vaues would be the same of STYLE element (all, screen, print,
handheld ...)
This doesn't really work because media queries are supposed to change
dynamically. The
Example 1.2.5 Delegation has a bug in it. The subworker defines a
function do, which I guess is technically ok, but then calls it like
this: do();. This triggers an exception. Let's rename the function
to something less evil.
-Ben
Alexey Proskuryakov wrote:
Nov 14, 2008, в 11:31 PM, Jonas Sicking написал(а):
Could you please explain how this scenario is affected by the port
being started? Messages are queued in closed ports until those are
started, so I think that it applies word to word to closed ports.
Where the
On Fri, Nov 14, 2008 at 4:33 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Hmm.. this makes a lot of sense for importScripts, but for XHR you probably
want the baseURI to be that of the opening page, since it's quite likely
that the opening page gave you a URI to open and process.
My expectation
On Fri, Nov 14, 2008 at 4:37 PM, Aaron Boodman [EMAIL PROTECTED] wrote:
On Fri, Nov 14, 2008 at 4:33 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Hmm.. this makes a lot of sense for importScripts, but for XHR you
probably
want the baseURI to be that of the opening page, since it's quite
Aaron Boodman wrote:
On Fri, Nov 14, 2008 at 4:33 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Hmm.. this makes a lot of sense for importScripts, but for XHR you probably
want the baseURI to be that of the opening page, since it's quite likely
that the opening page gave you a URI to open and
The changes look like improvements to me, but I have some questions.
1. Is there any particular reason why step 7 generate the list of
potential media resources is done in the synchronous part of the
algorithm? Would it for example be an error to consider playing sources
added in a loadstart
Jonas asked me about this in IRC, and specifically why I suggested
appCodeName (since everyone claims they are Mozilla). My thinking was:
a) Browser detection is a mess, scripts use everything on the
navigator object (often incorrectly) to try and figure out which
browser is which
b) HTML5 may
On Thu, 16 Oct 2008, Robert O'Callahan wrote:
I have added window.navigator.canPlayType(mimeType). It returns 1, 0,
or -1 to represent positive, neutral, and negative responses.
navigator.canPlayType could be confusing since authors might think it
includes media playable via plugins
35 matches
Mail list logo
