In short, you should mark functions and constant parameters with VAR as
well. The VAR element marks its content as incidental, as opposed to
elementary functions that do not need any special markup, like
SPAN CLASS=melfun sin VAR alpha;/VAR /SPAN
or
dVAR x/VAR sup2; = 2 VAR x/VAR dVAR
Ian Hickson skrev:
The spec itself has little annotation boxes on the left hand side that
documents where implementations stand, sort-of. There's also this wiki
page:
http://wiki.whatwg.org/wiki/Implementations_in_Web_browsers
There is also this wiki page:
2008/9/20 Daniel Cater [EMAIL PROTECTED]:
...
It wasn't backed out, just disabled by default for Firefox 3. See
https://bugzilla.mozilla.org/show_bug.cgi?id=415168. It can be
re-enabled by setting browser.send_pings to false in about:config.
Daniel.
Obviously I meant true, not false. The
Keryx Web wrote:
...
BTW, Gecko had an implementation of the ping attribute they backed out
due to spec changes. Is that part of the spec stable enough for them to
start working on again?
...
That part of the spec is subject of a long discussion thread and (as far
as I can tell) has no WG
On Sat, 20 Sep 2008, Keryx Web wrote:
BTW, Gecko had an implementation of the ping attribute they backed out
due to spec changes. Is that part of the spec stable enough for them to
start working on again?
I'm not aware of any outstanding technical feedback on the issue (though
not
Ian Hickson wrote:
On Sat, 20 Sep 2008, Keryx Web wrote:
BTW, Gecko had an implementation of the ping attribute they backed out
due to spec changes. Is that part of the spec stable enough for them to
start working on again?
I'm not aware of any outstanding technical feedback on the issue
On Sat, 20 Sep 2008, Julian Reschke wrote:
There aren't any changes planned; it's as stable as any part of HTML5
can get without any implementations locking it down. It could still
change in response to implementation feedback though.
Does that include the possibility of it getting
On Sat, Sep 20, 2008 at 4:13 AM, Kristof Zelechovski [EMAIL PROTECTED]
wrote:
In short, you should mark functions and constant parameters with VAR as
well.
The spec says that var represents a variable. To mark non-variables with
var is a misuse of markup; it's like surrounding computer
Ozob the Great wrote:
Making HTML that much richer would require
duplicating a large chunk of MathML, which is undesirable.
There's already ongoing work to allow MathML and SVG vocabularies to be
expressed in the text/html serialization of HTML5.
--
Benjamin Hawkes-Lewis
On Sat, Sep 20, 2008 at 6:41 PM, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
Ozob the Great wrote:
Making HTML that much richer would require duplicating a large chunk of
MathML, which is undesirable.
There's already ongoing work to allow MathML and SVG vocabularies to be
expressed in
Ozob the Great wrote:
Then var steps on MathML's toes: It duplicates functionality.
Not necessarily; a program variable should certainly not be marked up
with MathML.
On Sat, Sep 20, 2008 at 4:08 PM, Ozob the Great [EMAIL PROTECTED] wrote:
On Sat, Sep 20, 2008 at 6:41 PM, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
Ozob the Great wrote:
Making HTML that much richer would require duplicating a large chunk of
MathML, which is undesirable.
There's
On Sat, Sep 20, 2008 at 7:09 PM, Edward Z. Yang
[EMAIL PROTECTED] wrote:
Ozob the Great wrote:
Then var steps on MathML's toes: It duplicates functionality.
Not necessarily; a program variable should certainly not be marked up
with MathML.
Conceded. I believe that in a mathematical
On Sat, Sep 20, 2008 at 7:12 PM, Garrett Smith [EMAIL PROTECTED]wrote:
On Sat, Sep 20, 2008 at 4:08 PM, Ozob the Great [EMAIL PROTECTED]
wrote:
On Sat, Sep 20, 2008 at 6:41 PM, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
Ozob the Great wrote:
Making HTML that much richer would
14 matches
Mail list logo
