(Commenting on XXXSVG comments now since otherwise I might lose this
item of feedback.)
The attribute adjustment table seems to be missing the attributeName
attribute.
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
If attribute values were limited to ASCII, so would be the values for @ALT
and @TITLE. This would cause the same problem.
OTOH, attribute names are, with the pending unfortunate exception of EMBED.
Chris
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tab Atkins
On Fri, 7 Mar 2008, Alexey Proskuryakov wrote:
On Mar 3, 2008, at 6:11 PM, Jjgod Jiang wrote:
[...] I think we can suggest clients to simply treat encodings like
these as their biggest superset, for instance, treat GB2312 as
GB18030.
In my testing, it appears that IE 7 and Firefox 2 do
On May 22, 2008, at 12:23, Ian Hickson wrote:
EUC-KR - Windows-949
KS_C_5601-1987 - Windows-949
FWIW, x-windows-949 would be more correct given the current IANA
situation.
The list is missing tis-620, x-iso-8859-11 and iso-8859-11 which
should turn into x-windows-874.
Let me know
On Thu, 13 Mar 2008, �istein E. Andersen wrote:
On 5th June 2007, Øistein E. Andersen wrote:
(To do this properly, what we really ought to do is look for
C1 and undefined characters in all IANA charsets and semi-official
mappings to Unicode and check 1) whether the gaps can be filled
by
Ian Hickson wrote:
Summary:
* I've added a sandbox= attribute to iframe, which by default
disables a number of features and takes a space-separated list of
features to re-enable:
[snip list]
Unless I'm missing something, this attribute is useless in practice
because legacy browsers
Legacy browsers will use @SRC which must be filtered. They will ignore the
new content (whatever the attribute name will be) altogether so it need not
be filtered. Fallback @SRC can contain a URL to an error page saying Sorry,
not in your browser.
Chris
-Original Message-
From: [EMAIL
Ian Hickson wrote:
- by default, content in sandboxed browsing contexts, and any
browsing contexts nested in them
How do those nested browsing contexts come about, given that later you say:
- content in those browsing contexts cannot create new browsing
contexts or
1. Nested browsing contexts in a sandboxed frame cannot be created
dynamically but they can be defined by the inner markup.
2. If the frame is not allowed to execute scripts, setting location to
script should have no effect.
3. There is a potential discrepancy between applying parent width, which
WARNING: this email is sent to both the WhatWG and W3C Public HTML
list, as it is a proposal. Please be careful about where you
reply/follow-up to. The editors may have a preference (and if they
do, I hope they express it).
The following discussion is also in the attached proposal, but
On Thu, 3 Apr 2008, �istein E. Andersen wrote:
As suggested earlier, ISO 8859-9 is a proper subset of CP1254, and IE7
always uses the superset. [Actually, the name shown in the menu varies
-- Turkish (ISO) v. Turkish (Windows) --, but the underlying encoding
vector appears to be the
On Thu, 22 May 2008, Henri Sivonen wrote:
On May 22, 2008, at 12:23, Ian Hickson wrote:
EUC-KR - Windows-949
KS_C_5601-1987 - Windows-949
FWIW, x-windows-949 would be more correct given the current IANA situation.
Should I just changed the spec to strip leading x-s? That would deal
On Thu, 28 Jun 2007, �istein E. Andersen wrote:
1) Is it useful to handle unterminated entities followed by an
alphanumerical character like IE does? The number of documents for which
this actually helps might be small compared to the number of documents
that contain other, incorrigible
On Tue, 4 Mar 2008, �istein E. Andersen wrote:
On Fri, 29 Feb 2008 01:21:20 + (UTC), Ian Hickson wrote:
(I've made the characters not allowed in XML also not allowed in HTML,
with the exception of some of the space characters which we need to
have allowed for legacy reasons.)
The
Kristof Zelechovski wrote:
1. Nested browsing contexts in a sandboxed frame cannot be created
dynamically but they can be defined by the inner markup.
There was no mention of dynamically in Ian's proposal. My assumption
was that cannot create browsing contexts meant just that. If it
Ian Hickson wrote:
I'm thinking of introducing a
new attribute. I haven't worked out what to call it yet, but definitely
not src, source, src2, content, value, or data -- maybe
html or doc, though neither of those are great. This attribute would
take a string which would then be interpreted
Hi Dave,
If the W3C standardises time ranges through a URI approach, would
there still be a need to have a specification in the DOM or the HTML
code?
I am talking about this planned activity
http://www.w3.org/2008/01/media-fragments-wg.html and a scheme akin to
the one mentioned here
17 matches
Mail list logo
