I'd find these events useful and consistent too
All the more when you want to listen events on storage happening very
occasionally without the charge of listening other storage events happening
very often...
You might have some significant performance differences
-Message d'origine-
De
If browsers all send the referrer HTTP header, Webmaster might always put a
filter on incoming requests,
But it won't prevent other webmaster to get these resources tunneling it from
their own server sending a fake referrer header
If you want to strictly restrict cross-domain resources, the only
barcode reader)
Alexandre Morgaut
Wakanda Community Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
ns choose one from the filesystem, the camera, or even sometimes
some other web service
> Basically, there is no need to say anything about a barcode reader, if you
> have one in your user agent, just use it... It will work already.
Sorry, I may misunderstand what you mean... I think the
e.g. host would also
> mean normalising host via IDNA toASCII and friends. Not sure I'm fond
> of that.)
> * Advice on file URLs would be nice.
> * IDNA: what are your plans? IDNA2003 / IDNA2008 / UTS #46 / something
> else? It would be nice to get agreement on this.
> * Term
5550101",
hostname: "+15105550101",
href: "+15105550101?body=hello%20there",
parameters: {
body: "hello there"
}
pathname: "",
port: "",
protocol: "sms:",
searc
On 24 sept. 2012, at 14:08, Alexandre Morgaut wrote:
>
> sms:+15105550101?body=hello%20there
>
> {
>host: "+15105550101",
>hostname: "+15105550101",
>href: "+15105550101?body=hello%20there",
>
quot; might also be interpreted as part of the value
I think considering it as separator would introduce more problems that the ones
it could resolve (my 2 cents)
>
>> By the way, it would also be nice for the query part of this API to be
>> usable in isolation.
>
> +1
The q
y concern is just that "key" should probably be named "getKey" to avoid name
collision with parameter names
Alexandre Morgaut
Wakanda Community Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
>
> Only feedback left is the return types of set(), append(), and delete().
>
Maybe remove() would be better than delete() as delete is a reserved JS keyword
;-)
Alexandre Morgaut
Wakanda Community Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40
> having to re-encode the pixel data since that leads to loss of
> quality.
>
> / Jonas
Alexandre Morgaut
Wakanda Community Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
perspective a contributor to
> development of a conformance checker, I think in practice more user time is
> wasted by the existence of the current spec prohibition on unregistered/
> non-standard meta@name values than would be wasted by allowing arbitrary
> values.
>
> --Mike
>
> --
> Michael[tm] Smith http://people.w3.org/mike
Alexandre Morgaut
Wakanda Community Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
a lot of the time you don't need
> that power and at least in those cases I'd prefer using a more expressive
> way. The getElement methods aren't going away (and I think that's a good
> thing) and I believe it's a good idea we be consistent here and make
> DocumentFragments have these methods as well. Use the right tool for the
> job.
>
> Cheers,
> Jussi
Alexandre Morgaut
Wakanda Community Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
ET /pack1.zip/graph1.png?xywh=160,120,320,240
On 29 août 2013, at 12:02, Alexandre Morgaut wrote:
> Such concept make me think to something I already saw long time ago:
> - http://limi.net/articles/resource-packages/
> -
> http://unscriptable.com/2010/08/03/firefoxs-proposed-resour
On Jul 29, 2010, at 7:57 PM, Nicholas Zakas wrote:
> Proposed Interface Change:
>
> The easiest way to include such a change would be to augment the
> Storage::setItem() method with a third optional argument. So change from:
>
> setter creator void setItem(in DOMString key, in any data);
> Storage::setExpiration(in DOMString key, in TTL or expiration Date)
>
> (or Storage::setTTL() if you guys don't agree on the Date option)
>
> This might make sense, but I'm also not sure it's worth the additional API
> surface area. Plus I kind of like the idea of making it difficult for peo
Please ban this spammer
On Nov 10, 2010, at 9:20 AM, Alexandre Гоннов wrote:
> HD Video: http://agasearch.info/?full-hd-video.avi
>
> Mirror 1: http://uploading.com/files/zk4GO4lVbt/sample-video.avi
> Mirror 2: http://rapidshare.com/files/isbmPFLloD/sample-video.avi
> Mirror 3: http://www.4share
The HTML Table API provides powerful attributes like:
- "scope"
- "headers"
- "colspan"
- "rowspan"
All of them give informations about relationships between the table cells,
rows, and columns
It would be very helpful if:
- each "th" element could have a "cells" property which would be the HTM
Another approach:
The link tag is meant to support a "prefetch" value for the "rel" attribute
asking to preemptively cache the resource:
- http://blog.whatwg.org/the-road-to-html-5-link-relations#rel-prefetch
- http://davidwalsh.name/html5-prefetch
We can then write:
let the link HTML Eleme
> i'm not sure you need an execute(), you might benefit from an event
> listener to tell you if a resource has been prefetched. but this
> general path seems less icky to me than most if not all of the other
> paths suggested in this thread.
you will surely take benefit from the onload event
Ac
>> The link tag is meant to support a "prefetch" value for the "rel"
>> attribute asking to preemptively cache the resource:
>> - http://blog.whatwg.org/the-road-to-html-5-link-relations#rel-prefetch
>> - http://davidwalsh.name/html5-prefetch
>
> For to address the use-case, some event mechanism
On Feb 9, 2011, at 4:40 PM, Nicholas Zakas wrote:
I had chatted with a few folks about using rel=prefetch, but there seems to be
a lot of issues that would have to be resolved to get the behavior I'm after.
Prefetching in this way is very passive, currently implemented as happening
during user
n" a écrit :
> The draft specification defines 20+ medial event handler IDL attributes
> on HTMLElement. These events are non-bubbling and are always targeted
> at and tags, so I wonder if they wouldn't be better
> defined on HTMLMediaElement instead.
>
>David
Here some Proposals / Features requests
Any comment would be welcome
http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html
1) arguments
I think that "args", the third parameter of setTimeout & setInterval is not
enough described
Should arguments be an Array, or any "Array l
On Feb 28, 2011, at 8:19 PM, Boris Zbarsky wrote:
>> But well, the signature looks like there is only one parameter
>
> No. If there were only one parameter, the signature would say |in any
> args|. It actually says |in any... args| which means any number of
> arguments. See http://www.w3.o
n
specific namespace
if "document.getElementById()" is too long, why not coming back to the IE4
form "document.all()"
I would be more comfortable with at least a standard namespace global property
like "elements" on window than the current situation
Thoughts ?
All you have to do is convince the Trident, Webkit, and Presto teams...
> on the other hand I would love to hear from the latter two what their
> thoughts are.
Is there any registered bug on Opera and Webkit about this topic ?
Or have we got to create one ?
> So far the only feedback I&#
>
>> What are the use cases for readonly on?
>
> The primary one I've seen is to have a non-editable text input that the
> user can still select-and-copy from.
Well... could be enough for this use case ;-)
Alexandre Morgaut
Product Manager
4D SAS
60, rue d
Oops I did it again !!!
A direct Reply which did not include the whatgw list
Thanx Simon for pointing it out, the direct response was not done intentionally
;-)
So here my comments:
> Am 29.04.2011 um 11:34 schrieb Alexandre Morgaut:
>
>> Hi Simon,
>>
>> The user
ble
I'll check in our team for other potentials uses cases and look how much
"async" could already solve these.
Regards
Alexandre Morgaut
Product Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
gisterContentHandler/registerProtocolHandler... Feel free
to propose anything else.
We are also open to partnership and/or sponsorship proposals.
The event's official website is http://wakanday.org, but you can also track it
on Lanyrd at http://lanyrd.com/2011/wakanday/
Alexandre Morgaut
P
ere must be substantial
> benefit to typical users (not just ones who disable script) from
> having them available as declarative features.
Alexandre Morgaut
Product Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
ipulate the
list of options via JavaScript
But yes, without maybe the last point, it should be quite simple to implement.
Another point: the code managing autosuggestion in search bars is not running
in a document context, and don't need currently to take care of Cross-Origin
policy...
Is it just me or is the WHATWG Blog out of service ?
http://blog.whatwg.org/
Alexandre Morgaut
Product Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
Sorry
It looks to be back...
On 19 août 2011, at 17:09, Alexandre Morgaut wrote:
> Is it just me or is the WHATWG Blog out of service ?
>
> http://blog.whatwg.org/
>
>
>
>
> Alexandre Morgaut
> Product Manager
>
> 4D SAS
> 60, rue d'Alsace
>
tax), but
> could we at least lay this simple foundation for encouraging server-side
> portability (in a way that works well with existing syntax highlighters)?
>
> Thanks,
> Brett
Alexandre Morgaut
Wakanda Community Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
event.data property
I wonder now if such fetch API could be a better place to manage such use case
Regards,
Alexandre Morgaut
Wakanda Community Manager
4D SAS
60, rue d'Alsace
92110 Clichy
France
Standard : +33 1 40 87 92 00
Email :alexandre.morg...@4d.com
Web : www.4D.com
Thanks for the redirection Anne
On 23 juin 2014, at 13:42, Anne van Kesteren wrote:
> On Mon, Jun 23, 2014 at 1:36 PM, Alexandre Morgaut
> wrote:
>> I wonder now if such fetch API could be a better place to manage such use
>> case
>
> The plan is for response.body (the
38 matches
Mail list logo
