As an author I shall offer my 2 cents too.
First off, I'm for native implementations and all that markup and CSS can
do on _existing_ content.
Thus said, I prefer having JS manipulating the content with AJAX than
having the markup doing that.
Apart from the concept that markup itself is being
Now I tested the interface. Here the results, just for completeness.
- IE does have such a command. I had a bad time looking for it, because
I'm Italian and the Italian translation is really poor (Consenti
aggiornamento metadati, i.e. Allow metadata to be refreshed instead of
Allow meta refresh).
On Sun, 22 Mar 2015 15:06:40 +0100, Martin Janecke whatwg@prlbr.com
wrote:
I've done a few tests and provide links to them below the following
discussion.
...
Test 4: https://prlbr.de/2015/03/inline-svg-without-height.html
Test 5: https://prlbr.de/2015/03/inline-svg-without-size.html
Thank you, I'll have to test on IE and Opera. Does that interface interact
with refresh instruction given by the header too? (The answer could also
be negative, as the refresh response header has been introduced by
Netscape for what I know)
2015-03-24 5:17 GMT+01:00 Nils Dagsson Moskopp
I think I can firmly say that I'm not in the JS all the things camp. I do
see the reasoning behind this, but I'd like to point out that not everyone
in the world would like to use the MVC model. Personally, I don't mind it
(since it offers a logical separation of data, presentation, and
https://github.com/mozumder/HTML6
I’ll be updating that Github with more ideas and refinement about the proposal
with occasional feedback into this list. Since this is getting some attention
it’s probably better to place the ideas in a setting that can be
updated/modified than to discuss it
On Mar 24, 2015, at 4:15 PM, Andrea Rendine master.skywalker...@gmail.com
wrote:
I don't want to openly oppose to this project, as I'm anyway curious about
how it will be developed. It's only that I have seen a lot of elements used
outside their proper dynamics.
I don't see HTML as a
Hi everybody.
The title says all, so this time, short request and therefore short message.
The specification says that object elements' associated resource can be
treated as a nested browsing context. But it can't be specified with
iframe new S-attributes (@srcdoc, @sandbox and @seamless). I can
Note that it's perfectly fine to reference svg files from a picture
element, see e.g http://sarasoueidan.com/blog/svg-picture/.
Which means repeating the map construction for every SVG file. Of course if
the SVG is created by a script or a graphics application it can be done
easily, but this is
Hi Andrea,
Yes those are valid points, but the issue I was trying to point out was not
the (implied) semantics (they're great and should remain), but the forced
sectioning it brings.
Although the title is appropriate to carry the page's title, the h1 in
general should carry the page's/article's
Hey guys,
I've been worrying (maybe too much) about the nav element lately.
In my experience, it has become more of a burden than a help when it comes
to the document outline.
The nav element forces a new outline section, therefore requiring a
heading and (implicitly) requiring a heading to
On Fri, 20 Mar 2015 20:22:28 +0100, Martin Janecke whatwg@prlbr.com
wrote:
Am .03.2015, 13:10 Uhr, schrieb Simon Pieters sim...@opera.com:
Please leave out syntax proposals for now. What I think is needed first
to drive this forward is:
* Use cases. Why do you need this?
In general
Ping. Any thoughts from folks familiar with the history API definition?
This proposal resolves a high-profile issue we've received from a number of
major websites. As Majid said, mobile-optimized websites are being forced
to choose between the fullscreen UX users expect from websites on phones
At first sight I wouldn't define this case so impractical or senseless.
Looking at your example it looks like that the nav element is related
with the site itself (e.g. other articles, other sections of the site), not
with the page. If you had a heading element for the whole site (e.g. the
site
For the first time in my life I support JavaScript. But I want to see where
this idea will go.
Here other 2 virtual cents: please, if it ends up as a way to improve the
template element somehow compatibly with the current standard, and if it
reveals to be viable, try turning it into a proposal for
On Mar 24, 2015, at 9:51 PM, delfin del...@segonquart.net wrote:
Hi all:
I agree with you all you have quoted, Rendine.
* Neal : a problem in developing countries where low end devices are
the norm, is _de facto_ THE norme , and was the need of web
(standards).
*
Hi all:
I agree with you all you have quoted, Rendine.
* Neal : a problem in developing countries where low end devices are
the norm, is _de facto_ THE norme , and was the need of web
(standards).
* HTML6, if ever, must accomplish and adopt the so called
_retro-conditions_,
Hello!
By way of introduction, I'm an author who reads some of these mailing lists but
(almost) never replies.
This proposal is quite interesting, wanted to throw in my two cents as well:
1. Would you consider writing a polyfill/Javascript framework for this?
It seems to me that the
I see JavaScript as a useful tool that is seriously abused by many devs, I'm
against this. But if you do it, make damn sure it has proper CSP support.
On March 24, 2015 2:18:53 AM PDT, Bobby Mozumder mozum...@futureclaw.com
wrote:
https://github.com/mozumder/HTML6
I’ll be updating that Github
On Tue, Mar 24, 2015 at 1:06 PM, Tetsuharu OHZEKI saneyuki.s...@gmail.com
wrote:
Hi everybody.
I have a question about the definition of CanvasRenderingContext2D's
behavior.
The current spec about CanvasRenderingContext2D says the following:
Except where otherwise specified, for the 2D
Bobby Mozumder mozum...@futureclaw.com writes:
Besides, when was the last time you actually wrote a static HTML file?
Does anyone do that?
I assume you asked a rhetorical question. Still, the answer is “Yes”.
For every web site, people actually write templates, not HTML code.
This is
On 3/24/15 4:06 PM, Tetsuharu OHZEKI wrote:
But I think that, why don't CanvasRenderingContext2D use restricted
float type defined in WebIDL if these methods ignore the value when
its is not finite?
Because they want to ignore the value.
By the current WebIDL spec
On Mar 24, 2015, at 8:07 AM, Neal Gompa ngomp...@gmail.com wrote:
I think I can firmly say that I'm not in the JS all the things camp. I do
see the reasoning behind this, but I'd like to point out that not everyone
in the world would like to use the MVC model. Personally, I don't mind it
On Mar 24, 2015, at 8:19 AM, Andrea Rendine master.skywalker...@gmail.com
wrote:
As an author I shall offer my 2 cents too.
First off, I'm for native implementations and all that markup and CSS can
do on _existing_ content.
Thus said, I prefer having JS manipulating the content with AJAX
Hi everybody.
I have a question about the definition of CanvasRenderingContext2D's behavior.
The current spec about CanvasRenderingContext2D says the following:
Except where otherwise specified, for the 2D context interface,
any method call with a numeric argument whose value is infinite
or
I don't want to openly oppose to this project, as I'm anyway curious about
how it will be developed. It's only that I have seen a lot of elements used
outside their proper dynamics.
I don't see HTML as a templating language, but it's probably because I'm
tied to current use cases, so I don't see
26 matches
Mail list logo
