[whatwg] ad
Has there ever been a discussion about a dedicated element for ads, like ad? I’d like to review or otherwise propose the element, for at least on the surface, advertising may warrant dedicated markup. -- Jens Oliver Meiert http://meiert.com/en/ ☆ http://coderesponsibly.org/
Re: [whatwg] ad
2014-12-05, 11:41, Jens Oliver Meiert wrote:
Has there ever been a discussion about a dedicated element for ads, like ad?
Probably. What specific purposes would it serve?
The most obvious way of utilizing such markup, assuming it were commonly
used, would be to have
ad { display: none }
in a user style sheet. I think this suffices to show why such markup
would not be used.
Yucca
Re: [whatwg] ad
On Fri, Dec 5, 2014 at 4:45 AM, Jukka K. Korpela jkorp...@cs.tut.fi wrote:
2014-12-05, 11:41, Jens Oliver Meiert wrote:
Has there ever been a discussion about a dedicated element for ads, like
ad?
Probably. What specific purposes would it serve?
Yes. This question has been addressed in the rationale section of the wiki,
here
https://wiki.whatwg.org/wiki/Rationale#Why_isn.E2.80.99t_there_a_dedicated_element_for_advertisements.3F_.28e.g..2C_.3Cad.3E.2C_or_.3Cadvert.3E.2C_or_.3Cbanner.3E.2C_or_whatever.29
.
The most obvious way of utilizing such markup, assuming it were commonly
used, would be to have
ad { display: none }
in a user style sheet. I think this suffices to show why such markup would
not be used.
Yup, that's about the size of it, and why the proposal was rejected.
Cory
Yucca
Re: [whatwg] HTML tags.Panorama, Photo Sphere, Surround shots
On 2014-11-18 06:57, Paul Benedict wrote: Is it really the responsibility of HTML to be told about this? I wouldn't think so. My initial thoughts are that all such information should be encoded in the file format of the image. I am not saying such information exists (maybe partially though), but that's where I think it should reside. Cheers, Paul Yeah! Ideally a browser (or client) should be able to request the meta information for a image (if available), this would probably be better suited as part of HTTP/2. Instead of a HEAD request a client could do a META request which would be the same as a HEAD request but with all meta info the server can provide about the file (like lens/ISO etc. info). Server side something like Apache could let a handler fetch that info from a JPG file (maybe even a caching proxy to speed things up). A key:value pair would make sense I guess (with maybe a Meta- prefix). But yeah in HTML itself such would just really bloat up the HTML page itself (and one could always use AJAX and serverside scripting or similar to fetch such meta info). -- Roger Rescator Hågensen. Freelancer - http://www.EmSai.net/
Re: [whatwg] ad
https://wiki.whatwg.org/wiki/Rationale#Why_isn.E2.80.99t_there_a_dedicated_element_for_advertisements.3F_.28e.g..2C_.3Cad.3E.2C_or_.3Cadvert.3E.2C_or_.3Cbanner.3E.2C_or_whatever.29 I thought we may have touched it. That makes sense. Though I didn’t instantly think of the user style sheet one-liner ad would be begging for. -- Jens Oliver Meiert http://meiert.com/en/ ☆ http://uitest.com/
