on an attribute)
regards
Olav Junker Kjær
.
regards
Olav Junker Kjær
it somewhat gracefully (by ignoring
it).
regards
Olav Junker Kjær
Btw, in HTML5 class name handling is easier through the DOMTokenString
interface, you just write:
element.classNames.add(somethingThatIsOnlyVisibleOnScreen)
/olav
Dean Edwards wrote:
If I set element.style.display = block how do I hide it using a style
sheet when it is printed?
I dont think you should set element.style.display to block, if the
element should be visible only on screen and not in print. It would be
better to dynamically assign it a
of the spec is that a form must always be
submitted by a specific button. So if your UI allows you to submit a
form e.g. by clapping your hands once, the onclick event is still fired
on the default button and the name=value of the button is still submitted.
Olav Junker Kjær
Dean Edwards wrote:
- Date widget appearance: Once the date chooser popup widget has been
dismissed, the date in its correct localized format will be displayed
I agree but localisation is hard for us. I'm not sure how we are doing
that yet. Olav?
Thats the easy part. Using the built-in
space, shouting the label on the
element) is media dependent.
regards
Olav Junker Kjær
Wouldn't it be safer to declare the encoding in the js file itself?
It could be in a magic comment at the start of the document:
//@charset(utf8)
Not very elegant, but less error prone than to specify the encoding
everywhere the file is included.
regards
Olav Junker Kjær
Toshirou Takahashi wrote
as proprietary, and because Flash has
an even wider penetration (and better tools).
regards
Olav Junker Kjær
which is intended to cover
*web* applications. SVG is at least usable in IE through a plug-in for
IE, but realistically, anyone who needs interactive vector graphics on
the web is going to use flash.
regards
Olav Junker Kjær
as
documentation of the intention of the spec. Often I understand a feature
better by reading the use case, rather than by reading the precise
specification.
regards
Olav Junker Kjær
the same ground but which are
optimized for different use cases. A closer cooperation and sharing of
ideas between XForms and WF2 communities will certainly be a boon for
everyone. In the end, HTML extensions do belong in the W3C. So I'll be
optimistic now!
regards
Olav Junker Kjær
understand your reluctance to have unspecified behavior. I think
it might be useful to have a note saying you are not supposed to do
this in these cases, so the reader won't lose sleep trying to figure
out why the features is included in the spec.
regards
Olav Junker Kjær
* all the forms they are
associated with. :-)
Olav Junker Kjær
form at a time. (Along the same line, hitting enter when focus
is in a text field should only submit one form.)
regards
Olav Junker Kjær
a missing /b might be annoying but wont usually have serious
consequences in HTML (XHTML is different, of course). Still, this is the
only type of error DTD validation will catch.
regards
Olav Junker Kjær
rows is already supported in
CSS through the :nth-child pseudo-class.
regards
Olav Junker Kjær
, and it might make both specs clearer and more
focused.
regards
Olav Junker Kjær
Dean Edwards wrote:
It was my understanding (from reading previous threads) that there were
still some misgivings about the repetition model.
There doesn't seem to be too much discussion about the repetition model.
I think the reason some suggest dropping it from the spec, is that they
would
default to input type=text. This is not a big deal,
though, since we can just avoid giving the field a name attribute.
Regards
Olav Junker Kjær
21 matches
Mail list logo
