In http://www.whatwg.org/specs/web-apps/current-work/#dom-window-close it
is forbidden to close browsing contexts using the close() method when they
are opened by a user-initiated action. We think it would be better if that
were allowed, with the restriction that WebKit has, namely that once
startOffsetTime seem to leave people confused, I often have to explain it,
and yesterday I read the spec[5] and old emails and got confused myself.
It hasn't been implemented after almost 2 years.
Having the UTC time of the clip you're getting would be very useful. But
it'd be really nice
Thanks for putting this together Odin -- this has long been a point of
interest for all of us on the Popcorn.js dev team.
Rick
On Wed, Mar 7, 2012 at 5:56 AM, Odin Hørthe Omdal odi...@opera.com wrote:
startOffsetTime seem to leave people confused, I often have to explain it,
and yesterday I
On a and form elements you can specify a target attribute, e.g.
_blank. But sometimes you don't know whether to open in _self or _blank
at the time the link is clicked/the form is submitted.
I suggest that a server can specify a link target in an HTTP header,
e.g. Window-Target: _blank. The
On Wed, 07 Mar 2012 22:19:17 -, Christian Schmidt whatwg@chsc.dk
wrote:
I suggest that a server can specify a link target in an HTTP header,
e.g. Window-Target: _blank. The page would be equivalent to specifying
the same value in the form or a tag leading to the page. It should
(12/03/06 17:58), Kishore Bolisetty wrote:
But it doesn't talks about the behaviour - what if border is not specified
but bordercolor is specified? Looks like browsers have taken their own
implementations on this, Opera and Mozilla displays bordercolor only if
border is specified, where as
Thanks Ian for the clarification. What I understand from the comment is
that, when focused element is made display:none in this case, the focus
should be moved to body element if its there else we should blur the
focused element. There is bug for the same issue
Thanks Ian for the comment. There is already a bug filed in webkit -
https://bugs.webkit.org/show_bug.cgi?id=14443 which i was working on. I
will attach this thread for clarification there. I will try to fix the
issue asap.
Regards
--
Kaustubh
On Fri, Jan 27, 2012 at 4:23 AM, Ian Hickson