On Wed, Dec 14, 2011 at 2:00 AM, Ian Hickson i...@hixie.ch wrote:
I can remove the text one at a time, if you like. Would that be
satisfactory? Or I guess I could change the spec to say that the parser
should process the characters, rather than the tokenizer, since really
it's the whole
On Sun, Dec 11, 2011 at 1:21 PM, Leif Halvard Silli
xn--mlform-...@xn--mlform-iua.no wrote:
(which means
*other-language* pages when the language of the localization doesn't
have a pre-UTF-8 legacy).
Do you have any concrete examples?
The example I had in mind was Welsh.
Logical
Hi Nikhilesh,
I also brought this up in 2010, after working on the Comments solution for
the BBC.
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-December/029459.htm
l
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-December/029471.htm
l
As comment isn't completely backwards
On Fri, Dec 9, 2011 at 12:10 AM, James Graham jgra...@opera.com wrote:
It's not clear that device-width and device-height should be encouraged
since they don't tell you anything about how much content area is *actually*
visible to the user.
Why do media queries support querying the device
2011/12/19 Bronislav Klučka bronislav.klu...@bauglir.com:
I agree, additional API for this would be better
FileSaver is not exactly all you would need, because FileSaver is already
implemented e.g. in Chrome
to save file to browser file system (requestFileSystem).
requestFileSystem is not
On Mon, 19 Dec 2011 16:47:50 +0100, Henri Sivonen hsivo...@iki.fi wrote:
On Fri, Dec 9, 2011 at 12:10 AM, James Graham jgra...@opera.com wrote:
It's not clear that device-width and device-height should be encouraged
since they don't tell you anything about how much content area is
*actually*
Also sprach Anne van Kesteren:
It's not clear that device-width and device-height should be encouraged
since they don't tell you anything about how much content area is
*actually* visible to the user.
Knowing the device width/height could potentially be be used to decide
if users
On Monday 2011-12-19 17:17 +0200, Henri Sivonen wrote:
On Sun, Dec 11, 2011 at 1:21 PM, Leif Halvard Silli
xn--mlform-...@xn--mlform-iua.no wrote:
I discovered that UNICODE is
used as alias for UTF-16 in IE and Webkit.
...
Seemingly, this has not affected Firefox users too much.
It
On 19.12.2011 17:05, Glenn Maynard wrote:
2011/12/19 Bronislav Klučkabronislav.klu...@bauglir.com:
I agree, additional API for this would be better
FileSaver is not exactly all you would need, because FileSaver is already
implemented e.g. in Chrome
to save file to browser file system
On Mon, Dec 19, 2011 at 2:06 PM, Bronislav Klučka
bronislav.klu...@bauglir.com wrote:
On 19.12.2011 17:05, Glenn Maynard wrote:
2011/12/19 Bronislav Klučkabronislav.klu...@bauglir.com:
I agree, additional API for this would be better
FileSaver is not exactly all you would need, because
On 19.12.2011 23:15, Eric U wrote:
On Mon, Dec 19, 2011 at 2:06 PM, Bronislav Klučka
bronislav.klu...@bauglir.com wrote:
On 19.12.2011 17:05, Glenn Maynard wrote:
2011/12/19 Bronislav Klučkabronislav.klu...@bauglir.com:
I agree, additional API for this would be better
FileSaver is not
11 matches
Mail list logo
