On 03/24/2015 04:50 PM, Michael A. Peters wrote:
I see JavaScript as a useful tool that is seriously abused by many devs, I'm
against this. But if you do it, make damn sure it has proper CSP support.
I would like to clarify that when I say I am against this, I am not
opposed to the
On 24.03.2015 21:29, Bobby Mozumder wrote:
Also, I'm a little terrified of having SQL directly in the markup. There's
so much potential for that to go horribly wrong. Personally, I feel things
that involve data retrieval should be better handled by endpoints that
return HTML, XML, or JSON.
On 03/25/2015 12:39 AM, Janusz Majnert wrote:
OK. This makes no sense for me.
So you propose that the server does simple translation of SQL from url
to actual query, but you don't see any security issue with this?
If on the other hand you're proposing that the server validates the sql
sent
On Tue, Mar 24, 2015 at 11:06 PM, Andrea Rendine
master.skywalker...@gmail.com wrote:
Is there a reason why it does not apply to object browsing
contexts?
Yes. object does too much (it can handle both browsing contexts and
embedding contexts) and therefore we shouldn't extend it more. Both
On Tue, 24 Mar 2015 15:41:26 +0100, Andrea Rendine
master.skywalker...@gmail.com wrote:
why
not improving an existing feature instead of finding so many expensive
workarounds? It'd allow authors the choice to use between 2 different
tools
for different cases.
See
why doesn't the document interface expose the refresh timeout?
Because nobody implemented it and nobody asked for it (until now).
I don't know whether to feel proud or guilty about that.
http://www.phpied.com/files/location-location/location-location.html .
This list does not show that anyone
On Tue, 24 Mar 2015 02:41:30 +0100, Andrea Rendine
master.skywalker...@gmail.com wrote:
Hi everybody!
A request starting from meta element and its refresh state: why doesn't
the document interface expose the refresh timeout?
Because nobody implemented it and nobody asked for it (until now).
why not improving an existing feature
See https://wiki.whatwg.org/wiki/FAQ#Where.27s_the_harm_in_adding.E2.80.94
Yes, I think I should have expressed it better. Why not improving *this*
specific feature?
I'm aware that older elements could end up being incompatible with use
cases they have
On Thu, Mar 19, 2015 at 6:31 PM, Majid Valipour maji...@chromium.org wrote:
partial interface History {
void pushState(in any data, in DOMString title, in optional DOMString
url, in optional StateOptions options);
void replaceState(in any data, in DOMString title, in optional DOMString
I understand the reason.
Thank you!
Tetsuharu OHZEKI
2015/03/25 午前5:37 Boris Zbarsky bzbar...@mit.edu:
On 3/24/15 4:06 PM, Tetsuharu OHZEKI wrote:
But I think that, why don't CanvasRenderingContext2D use restricted
float type defined in WebIDL if these methods ignore the value when
its is
On 25/03/2015 14:54 , Anne van Kesteren wrote:
The only suggestion I have is that instead of having four-argument
methods we might want to consider introducing two new methods that
take a dictionary. E.g. history.push() and history.replace(). Giving
the page more control over the scroll position
On Wed, Mar 25, 2015 at 3:21 PM, Andrea Rendine
master.skywalker...@gmail.com wrote:
Yes, I think I should have expressed it better. Why not improving *this*
specific feature?
That's generally not how we do things. We don't start looking at an
existing set of features and figure out how we can
Instead, we start by figuring out what problems need solving.
Which is what has been done for this subject, I guess.
PROBLEM: image maps, intended as shaped link areas related to specific
regions of an image are a fairly requested feature. Unfortunately, as
current solutions are not responsive
On Wed, Mar 25, 2015 at 10:03 AM, Andrea Rendine
master.skywalker...@gmail.com wrote:
Instead, we start by figuring out what problems need solving.
Which is what has been done for this subject, I guess.
PROBLEM: image maps, intended as shaped link areas related to specific
regions of an image
Sorry for arriving so late to the party...
I would like to update this thread on what has been happening around
canvas.toBlob in Blink.
First of all, there was an attempt at implementing canvas.toBlob a couple
years ago, back when Chromium was using WebKit. The experience revealed
that the API
On Wed, Mar 25, 2015 at 4:28 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Thu, Mar 26, 2015 at 8:40 AM, Justin Novosad ju...@google.com wrote:
Eliminating the transit through canvas also
allows for fast paths for capturing blobs from video, img, svg, URLs,
to name a few.
With new
On Thu, Mar 26, 2015 at 9:43 AM, Justin Novosad ju...@google.com wrote:
createImageBitmap(myImageSource).then(function (image) {
image.toBlob().then(admireYourShinyNewBlob); });
Oh, right. Sorry! Of course :-).
Rob
--
oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo
On Wed, Mar 25, 2015 at 11:41 PM, Anne van Kesteren ann...@annevk.nl
wrote:
On Fri, Mar 20, 2015 at 11:15 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
My understanding is that the current consensus proposal for canvas in
Workers is not what's in the spec, but this:
On Thu, Mar 26, 2015 at 8:40 AM, Justin Novosad ju...@google.com wrote:
One idea we've been brewing that has not surfaced on this thread so far is
that of having an ImageBitmap.toBlob(), which would return a Promise. Also,
ImageBitmap should be transferable. This idea is just partially baked
Is this really something we should tie to the pushState/replaceState API?
It seems like websites that lazily add more content as the user scroll
down, like the facebook feed or twitter feed, might not use
pushState/replaceState, but would still like to handle restoring
scroll position themselves.
One of the 2 objections, I'd say. But the second is probably a matter of
implementation.
SVG makes it unclear what's the actual active area when navigating through
tab key.
2015-03-25 19:32 GMT+01:00 Tab Atkins Jr. jackalm...@gmail.com:
On Wed, Mar 25, 2015 at 10:03 AM, Andrea Rendine
On Mar 25, 2015, at 3:39 AM, Janusz Majnert j.majn...@samsung.com wrote:
OK. This makes no sense for me.
So you propose that the server does simple translation of SQL from url to
actual query, but you don't see any security issue with this?
If on the other hand you're proposing that the
Am .03.2015, 12:50 Uhr, schrieb Andrea Rendine
master.skywalker...@gmail.com:
[…] IE11 doesn't scale SVG as noticed about previous versions.
Thanks Andrea (also for your further feedback on the test cases), that is
good to know.
Am .03.2015, 14:36 Uhr, schrieb Erik Dahlström e...@opera.com:
A workaround for the bug in IE9+ is to add a wrapper element that does
the responsive sizing.
Something along the lines of http://jsfiddle.net/vo1ofz0w/1/.
That's very helpful in practice, thanks! It didn't work 100% correctly
yet (it pushes the figcaption away when the window is bigger than
Am .03.2015, 16:08 Uhr, schrieb Simon Pieters sim...@opera.com:
[…]
It seems to me that there are two use cases:
1. variable-size image map
2. art direction image map
(1) is more common than (2).
Yes, you're right.
If there is implementor interest, I think it makes sense to make map
On Wed, Mar 25, 2015 at 1:22 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Wed, Mar 25, 2015 at 11:41 PM, Anne van Kesteren ann...@annevk.nl
wrote:
On Fri, Mar 20, 2015 at 11:15 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
My understanding is that the current consensus proposal
On Fri, Mar 20, 2015 at 11:15 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
My understanding is that the current consensus proposal for canvas in
Workers is not what's in the spec, but this:
https://wiki.whatwg.org/wiki/WorkerCanvas
See Canvas in Workers threads from October 2013 for the
27 matches
Mail list logo
