features is starting to get worrisome.
--
Anne van Kesteren
http://annevankesteren.nl/
recall which) and it seemed browsers were using the first code
point found in the index. I hope that behavior is mostly consistent
without much additional special casing, but I have yet to test the
encoders.
--
Anne van Kesteren
http://annevankesteren.nl/
should write
some blog entry to summarize the whole exercise in case implementors need
convincing.
http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html#big5
--
Anne van Kesteren
http://annevankesteren.nl/
://bugzilla.mozilla.org/show_bug.cgi?id=735031 so maybe I am missing
something?
Cheers,
--
Anne van Kesteren
http://annevankesteren.nl/
On Fri, 06 Apr 2012 16:25:20 +0200, Doug Schepers schep...@w3.org wrote:
What's the rationale for restricting what authors (or users) can make
fullscreen?
You cannot render arbitrary SVG elements without a root svg element as
far as I know.
--
Anne van Kesteren
http://annevankesteren.nl/
the size of ::backdrop to be adjusted
by setting the top/left/bottom/right properties. Does that make sense?
--
Anne van Kesteren
http://annevankesteren.nl/
/Overview.html
Looking forward to dialog!
--
Anne van Kesteren
http://annevankesteren.nl/
-ancestor probably not. What are the new default styles going
to be?
--
Anne van Kesteren
http://annevankesteren.nl/
On Fri, 30 Mar 2012 14:00:38 +0200, Anne van Kesteren ann...@opera.com
wrote:
Ideally someone does detailed content analysis to figure out what the
best path forward is here, though I'm not entirely sure how.
I still don't know how, but thanks to Simon Pieters I gathered some URLs
from
On Wed, 04 Apr 2012 19:31:22 +0200, Tab Atkins Jr. jackalm...@gmail.com
wrote:
On Wed, Apr 4, 2012 at 1:05 AM, Anne van Kesteren ann...@opera.com
wrote:
How does this work for nested browsing contexts? Currently using iframe
allowfullscreen (not in HTML yet) you can fullscreen elements
this would break URLs where entities
are used to encode non-ASCII code points in the query component.
--
Anne van Kesteren
http://annevankesteren.nl/
was to do away with that so that
authors do not have to implement the parsing logic anymore.
--
Anne van Kesteren
http://annevankesteren.nl/
to figure out what the best
path forward is here, though I'm not entirely sure how.
--
Anne van Kesteren
http://annevankesteren.nl/
there, is unclear.
Given the information from Microsoft indicated at the start of this email
I sort of think maybe just following Internet Explorer here is the best
way forward, combined with strongly discouraging the usage of big5.
--
Anne van Kesteren
http://annevankesteren.nl/
.
Some help as to how best to proceed would be appreciated.
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 28 Mar 2012 12:18:41 +0200, Anne van Kesteren ann...@opera.com
wrote:
I'm not sure what to do with big5 and big5-hkscs. After generating all
possible byte sequences (lead bytes 0x81 to 0xFE, trail bytes 0x40 to
0x7E and 0xA1 to 0xFE) and getting the code points for those in various
but a
falsy JS value. |noEOF| ?
Peter Beverloo suggests stream on IRC. I like it.
Opinions on one object type (Encoding) vs. two (Encoder, Decoder) ?
Two seems cleaner.
--
Anne van Kesteren
http://annevankesteren.nl/
encodings which refers to the likes of euc-kr and shift_jis.
Yeah, I suspect we'll get it right once put in a draft :-)
--
Anne van Kesteren
http://annevankesteren.nl/
is a node object in the platform.
--
Anne van Kesteren
http://annevankesteren.nl/
On Thu, 22 Mar 2012 10:19:30 +0100, Anne van Kesteren ann...@opera.com
wrote:
They can use the prefixed variants :-) If we have to use a prefix
String seems better, as Text is a node object in the platform.
Simon pointed out Text as prefix is probably better (it is used elsewhere
whether more bytes are coming (defaults to false), but I'm not sure of the
chances that would be used correctly. The reasons you outline are probably
why many browser implementations deal with EOF poorly too.
--
Anne van Kesteren
http://annevankesteren.nl/
() and tracks state for both:
enc = new Encoding(gb18030)
bytes1 = enc.decode(string1)
string2 = enc.encode(bytes2)
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 14 Mar 2012 23:53:12 +0100, Glenn Maynard gl...@zewt.org wrote:
On Wed, Mar 14, 2012 at 6:52 AM, Anne van Kesteren ann...@opera.com
wrote:
If we can make it a deterministic, unchanging, and defined algorithm, I
think that would actually be acceptable. And ideally we do define
those.
And not go beyond what is defined/allowed in:
http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html
--
Anne van Kesteren
http://annevankesteren.nl/
can enter the existing market more
easily and existing browsers interpret existing content in the same way.
--
Anne van Kesteren
http://annevankesteren.nl/
the
user navigates the newly opened browsing context (and gains a history), it
can no longer be closed.
--
Anne van Kesteren
http://annevankesteren.nl/
done DOMStringList can be moved to the historical section of the
DOM (aka the graveyard).
--
Anne van Kesteren
http://annevankesteren.nl/
user
selection to have neither a body element nor a root element, if the
dragenter event handler for the immediate user selection deletes the root
element.)
--
Anne van Kesteren
http://annevankesteren.nl/
the current event name, not the event where it was
created.
--
Anne van Kesteren
http://annevankesteren.nl/
implements this proposal.
--
Anne van Kesteren
http://annevankesteren.nl/
during all events when dropping a file, instead of
just the drop event.
* It can drag selections between inputs (move) or from the page into an
input (copy) - the API is not required for this.
* When dragging a link, it adds an extra dummy URL into the .types
collection
--
Anne van Kesteren
support space-separated values for both
add() and remove() in the near future.
--
Anne van Kesteren
http://annevankesteren.nl/
UTF-8 and not accept anything else.
--
Anne van Kesteren
http://annevankesteren.nl/
, or otherwise, one
main canvas layer.
That would require special casing canvas in
http://dev.w3.org/csswg/cssom-view/#scroll-an-element which I'm not sure
is a good idea. Why don't you just dispatch a synthetic scroll event?
--
Anne van Kesteren
http://annevankesteren.nl/
it updates the
concept-document-url concept from DOM rather than introducing its own new
concept (you still need to introduce the current one though).
--
Anne van Kesteren
http://annevankesteren.nl/
On Sat, 21 Jan 2012 16:23:31 +0100, Leif Halvard Silli
xn--mlform-iua@målform.no wrote:
Ian Hickson on Fri Jan 20 14:31:01 PST 2012:
On Tue, 26 Jul 2011, Christoph Päper wrote:
Anne van Kesteren:
I'm still trying to get HTML and browsers to change so that attribute
values always match case
shift_jis characters here.
It seems that IE uses the same converter both iso-2022-jp and shift_jis.
I have filed a bug on Opera to become more strict like Webkit/Gecko. If
there is some evidence that approach is wrong though, we can turn it
around.
--
Anne van Kesteren
http://annevankesteren.nl/
On Sun, 08 Jan 2012 15:32:47 +0100, Anne van Kesteren ann...@opera.com
wrote:
On Sun, 08 Jan 2012 01:37:14 +0100, NARUSE, Yui nar...@airemix.jp
wrote:
== iso-2022-jp
=== The to Unicode algorithm
Based on iso-2022-jp state
= ASCII state
== Based on octet:
=== Otherwise
.
http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html
Feedback welcome!
--
Anne van Kesteren
http://annevankesteren.nl/
encodings - should do. See:
http://bugzilla.validator.nu/show_bug.cgi?id=890
Well yes, that's why I'm planning to define utf-16 more in line with
implementations (and render the current text obsolete I suppose).
--
Anne van Kesteren
http://annevankesteren.nl/
with that, that would be
great.
--
Anne van Kesteren
http://annevankesteren.nl/
special meaning.
That does not all suggest we should do the same for numerous other
encodings unrelated to utf-16.
--
Anne van Kesteren
http://annevankesteren.nl/
(of utf-16 / utf-16be) and is removed from the output.
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 21 Dec 2011 04:40:10 +0100, Mark Callow callow_m...@hicorp.co.jp
wrote:
On 20/12/2011 20:01, Anne van Kesteren wrote:
[3]http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html
This is a great start. A few comments
It seems weird to use Windows' names rather than the iso names
://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html
--
Anne van Kesteren
http://annevankesteren.nl/
in this day and age.
--
Anne van Kesteren
http://annevankesteren.nl/
versions without stepping on the toes of the other features
that might use the meta tag.
You do not create a conflict by adding new attributes. That makes no sense.
[1] http://dev.w3.org/html5/spec/Overview.html#the-meta-elemen
--
Anne van Kesteren
http://annevankesteren.nl/
or link.
--
Anne van Kesteren
http://annevankesteren.nl/
in
http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec though.
--
Anne van Kesteren
http://annevankesteren.nl/
;). That is often
faster than looking the character up somehow.
--
Anne van Kesteren
http://annevankesteren.nl/
of the above)
We can just add additional attributes to meta you know. We have done the
same for link. E.g. for link rel=icon you can specify a sizes
attribute.
--
Anne van Kesteren
http://annevankesteren.nl/
had to figure this out at some point.)
--
Anne van Kesteren
http://annevankesteren.nl/
and a common pattern. And seems like a much better alternative
than changing the HTML parser. Especially changing the way head is
parsed is hairy. Every new element we introduce there will cause a body
to be implied before it in down-level clients. That's very problematic.
--
Anne van Kesteren
http
a new element
this way?
--
Anne van Kesteren
http://annevankesteren.nl/
:
XHR.timeRemaining = estimated time left in ms
XHR.completionTime = a Date object representing the estimated completion
time
XHR.transferRate = upload/download speed, measured in Kbps, as an
integer.
Did you look at progress events?
--
Anne van Kesteren
http://annevankesteren.nl/
can find it here:
http://blog.whatwg.org/
Everyone who wants can write for the WHATWG blog:
http://blog.whatwg.org/submit-article
--
Anne van Kesteren
http://annevankesteren.nl/
forums and wiki, a blog, a
Twitter account. Each of those has proven successful I think. Not always
to the same people, but I think that is the value. By giving people choice
in how to participate we make it more easy for them to do so.
--
Anne van Kesteren
http://annevankesteren.nl/
the situation.
--
Anne van Kesteren
http://annevankesteren.nl/
On Mon, 21 Nov 2011 16:35:09 +0100, Nils Dagsson Moskopp
n...@dieweltistgarnichtso.net wrote:
Anne van Kesteren ann...@opera.com schrieb am Mon, 21 Nov 2011
15:14:16 +0100:
I personally had a number of
useful technical discussions on Google+. Maybe some of those will
take place on the WHATWG
since Document is what you
need to observe anyway for changes.
--
Anne van Kesteren
http://annevankesteren.nl/
(of events). E.g. if you have a descendant B
which has two descendants each with a fullscreen element. I guess you can
do them based on the stack order of B.
--
Anne van Kesteren
http://annevankesteren.nl/
declarations
make sense.
I also added transition:none to :fullscreen-ancestor per the comment that
was present in the draft.
Latest draft:
http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html#rendering
--
Anne van Kesteren
http://annevankesteren.nl/
On Mon, 14 Nov 2011 21:25:38 +0100, Robert O'Callahan
rob...@ocallahan.org wrote:
On Tue, Nov 15, 2011 at 1:38 AM, Anne van Kesteren ann...@opera.com
wrote:
I have removed background:black as the way the rendering is defined at
the moment is that it cannot be overridden unless !important
to it.
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 09 Nov 2011 09:52:43 -0800, Boris Zbarsky bzbar...@mit.edu wrote:
On 11/9/11 9:25 AM, Anne van Kesteren wrote:
It seems wrong to me to add new features to obsoleted features. If there
are good reasons for using frame, maybe it should be made conforming.
If there are no such reasons
case with the user exiting fullscreen before the events
have dispatched. Accounting for it seems like needless complexity. Having
the event dispatch twice combined with simply checking
document.fullscreenElement seems sufficient.
--
Anne van Kesteren
http://annevankesteren.nl/
their
(non-functioning) fullscreen buttons while their
document/parent/ancestor documents are fullscreen.
I made this change for now to keep the initial version simple.
--
Anne van Kesteren
http://annevankesteren.nl/
fullscreen element if something is fullscreen.
Third, perhaps fullscreenchange should be split into fullscreenon and
fullscreenoff events?
What are the use cases to distinguish them?
--
Anne van Kesteren
http://annevankesteren.nl/
that exiting exits everything which is quite odd.
--
Anne van Kesteren
http://annevankesteren.nl/
valid and
|text/plain ; charset=iso-8859-1| is perfectly valid too.
We do not want to sniff text/plain more than strictly necessary.
--
Anne van Kesteren
http://annevankesteren.nl/
Document.fullscreen as it's a subset of
Document.fullscreenElement
I realize this is not what everyone wants. But this seemed the simplest
subset of what everyone desired and a pretty good start from where we can
enhance going forward.
Kind regards,
--
Anne van Kesteren
http://annevankesteren.nl/
DOM Range has been folded into DOM4 so it should be removed as reference
from HTML. At one place it is referenced as defining text selections. That
is now done by the Editing specification.
--
Anne van Kesteren
http://annevankesteren.nl/
On Thu, 20 Oct 2011 10:20:57 +0900, Chris Pearce cpea...@mozilla.com
wrote:
On 19/10/2011 5:40 p.m., Anne van Kesteren wrote:
1) How much should UI-based and API-based fullscreen interact? To me
it seems nice if pressing F11 would also give you fullscreenchange
events
On Tue, 18 Oct 2011 10:33:42 +0900, Anne van Kesteren ann...@opera.com
wrote:
Site A embeds site B. Site A goes fullscreen. Site B does
requestFullscreen(). Site B does exitFullscreen(). Site A is no longer
fullscreen.
Either we need to base fullscreen on browsing contexts rather than
solely the UI, or both can be done using solely the
API. It would be confusing to users I think if you got different results
here.
--
Anne van Kesteren
http://annevankesteren.nl/
of nesting remains is no larger than required for the presentation
scenario mentioned above.
Is that an acceptable limitation? Alternatively we could postpone the
nested fullscreen scenario for now (i.e. make requestFullscreen fail if
already fullscreen).
--
Anne van Kesteren
http
an event, also asynchronous, that is dispatched when
the invocation did not succeed. Naming ideas so far: fullscreendeny and
fullscreenerror.
--
Anne van Kesteren
http://annevankesteren.nl/
out of fullscreen mode?
The current plan is that if any of the browsing contexts with non-null
fullscreen element is navigated you exit fullscreen.
--
Anne van Kesteren
http://annevankesteren.nl/
fullscreen.
Either we need to base fullscreen on browsing contexts rather than
top-level browsing contexts (how?) or give up on this use case.
--
Anne van Kesteren
http://annevankesteren.nl/
as that seemed cleaner
and easier to type. I also used enter and exit rather than request
and cancel as they seemed somewhat nicer too. I'm less attached to this
latter change though.
--
Anne van Kesteren
http://annevankesteren.nl/
. It seems better to just let it
function per its normal rules and have any such attributes be
non-conforming and ignored.
--
Anne van Kesteren
http://annevankesteren.nl/
simply return the one for #a.
--
Anne van Kesteren
http://annevankesteren.nl/
,
requestFullScreenWithKeys() seems unneeded.
--
Anne van Kesteren
http://annevankesteren.nl/
Is the event dispatched in the same task that makes the element or
document go full screen?
--
Anne van Kesteren
http://annevankesteren.nl/
context, the user agent?
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 12 Oct 2011 22:18:04 +0900, Henri Sivonen hsivo...@iki.fi wrote:
On Wed, Oct 12, 2011 at 11:56 AM, Anne van Kesteren ann...@opera.com
wrote:
Given the way Mac OS handles full screen applications I wonder whether
requestFullScreenWithKeys() is needed. A toolbar will always appear
On Thu, 13 Oct 2011 11:26:20 +0900, Chris Pearce cpea...@mozilla.com
wrote:
On 12/10/2011 10:35 p.m., Anne van Kesteren wrote:
Is cancelFullScreen() synchronous or should it queue a task?
Synchronous, so that Document.fullScreen immediately reflects the state
change? Why would it need
the crossorigin attribute at all? That is
how I envisioned CORS to work for img.
--
Anne van Kesteren
http://annevankesteren.nl/
out with writing tests, but I
have no ideas on how to test this in an automated way (apart from simple
IDL tests).
--
Anne van Kesteren
http://annevankesteren.nl/
in the end. One advantage I can see about
img crossorigin still displaying the image is that the request does not
use cookies. Not displaying the image probably makes debugging easier
however.
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 04 Oct 2011 20:55:28 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/4/11 2:44 PM, Anne van Kesteren wrote:
On Tue, 04 Oct 2011 20:32:02 +0200, Ian Hickson i...@hixie.ch wrote:
The idea is that if the server explicitly rejected the CORS request,
then
the image should not be usable
.
--
Anne van Kesteren
http://annevankesteren.nl/
that. The advantage being that only changes
on the server are required.
--
Anne van Kesteren
http://annevankesteren.nl/
left
for three months. It should be better now.)
--
Anne van Kesteren
http://annevankesteren.nl/
string.
--
Anne van Kesteren
http://annevankesteren.nl/
/links.html#link-type-help) exactly, but
close enough?
If there is no actual hyperlink, using a link relation does not make sense.
--
Anne van Kesteren
http://annevankesteren.nl/
browsers (I haven't checked how IE10 behaves yet). To me this
seems like an unnecessary limitation.
Initially submit() caused validation to be done but that broke deployed
content.
What is the reason for wanting this?
--
Anne van Kesteren
http://annevankesteren.nl/
browsers will handle CORS here though.
--
Anne van Kesteren
http://annevankesteren.nl/
this specification at the moment)? I'm asking because
Opera also support SSEs and CORS would probably be high in demand with
this specification I guess.
Yes. (Though we will probably introduce CORS support phased, leading with
XMLHttpRequest.)
--
Anne van Kesteren
http://annevankesteren.nl/
://caniuse.com/#search=eventsource
http://www.opera.com/docs/specs/
--
Anne van Kesteren
http://annevankesteren.nl/
601 - 700 of 1655 matches
Mail list logo
