| 06:43 | <sideshowbarker> | https://stackoverflow.com/questions/71136656/corp-blocking-an-obviously-same-origin-request |
| 07:58 | <annevk> | Left a reply |
| 07:58 | <sideshowbarker> | thanks |
| 11:20 | <Seirdy> | Are there any microdata vocabularies besides schema.org? I know there are a bunch for rdfa (dublin core, creativecommons, DOAP, FOAF, etc) but I don't know of any schema.org alternatives for microdata. |
| 11:25 | <completesagalego> | yes it does |
| 11:31 | <Seirdy> | I noticed microformats.org/profile/hcard but I don't see a point in using those over classes because classes have more universal support. I do like schema.org's more detailed info. i would use rdfa so i could make use of dublin core, foaf, etc. but microdata has more support than rdfa (used by readability, chromium DOM distiller, less error prone on search engines, and some others). which is why I ask. Mixing microformats classnames and microdata syntax is okay but dealing with a third format kinda kills the fun of structured data for me. |
| 11:36 | <Seirdy> | yes it does |
| 11:40 | <Seirdy> | I know it's possible to create ad-hoc vocabs but I'm more interested in vocabs that are actually standardized or supported by something |
| 16:02 | <aja> | Seirdy: not exactly on point, but https://www.w3.org/TR/dpub-aria-1.1/ may be of interest |
| 17:03 | <Domenic> | annevk: I would appreciate help advising Noam Rosenthal on what to do with trying to integrate resource timing and media fetches, given how un-rigorous media fetches are today. https://github.com/whatwg/html/pull/7553#discussion_r805082633 |
| 17:29 | <annevk> | Thanks for the ping, I left some pointers to prior work and a very high-level suggestion for what the setup might look like. Hope that helps. |
| 17:34 | <Noam Rosenthal> | thanks annevk, it definitely helps. I split it from the rest of the content for now and will get back to it with those pointers |
| 17:42 | <wayneca> | What exactly is the abbr attribute on the TH element used for? The only example I've found (on the W3Schools site) just shows it being placed in the TH tag, but does not describe what you would do with it. It seems to only be useful as informational to anyone viewing the page source. |
| 17:45 | <Domenic> | What exactly is the abbr attribute on the TH element used for? The only example I've found (on the W3Schools site) just shows it being placed in the TH tag, but does not describe what you would do with it. It seems to only be useful as informational to anyone viewing the page source. |
| 17:47 | <wayneca> | I see. Thanks for the explanation. Because I don't typically delve that far into the behind the scenes part of web-browsing I don't usually think of these things. I just want to make sure my understanding is correct as I build my list of attributes and what they do. |
| 18:01 | <wayneca> | The html5 specification shows autofocus being a global attribute (it says HTML elements, but W3Schools lists those as being Global Attributes), but the W3Schools site lists autofocus as belonging to <button>, <input>, <select>, <textarea>. Is it global or is it specific to only these tags? |
| 18:05 | <annevk> | wayneca: W3Schools is not an authoritative source of information (it also doesn't belong to the W3C) |
| 18:05 | <wayneca> | OK. I just use it because it has much information in one place that is more easily digested than the specification is. It also agrees with the specification in many things. I have noticed that there are some things in the specification that are absent in the W3Schools information. Based on this response I will take the specification as being correct when W3Schools shows something different. |
| 18:57 | <Seirdy> | OK. I just use it because it has much information in one place that is more easily digested than the specification is. MDN is generally a far better (non-authorative) source than w3schools for learning. but nothing beats the specs |
| 18:59 | <wayneca> |
I agree with that sentiment totally. The spec is the authoritative source. It's just not that easy to understand in many ways. |
| 19:02 | <Seirdy> | oh definitely, it's usually written for implementers first and authors second. and it needs to favor comprehensiveness over approachability, and it has to be extra neutral when making recommendations. and it can't give recommendations too influenced by the existing landscape/implementations. hence the use for MDN. |
| 19:03 | <Andreu Botella> | There's https://html.spec.whatwg.org/dev/ |
| 19:04 | <Seirdy> | it's just the source of truth that has the last word when parties disagree. |
| 19:04 | <Seirdy> | and a reference |
| 19:04 | <wayneca> | Thanks, Andreu. This is the first I've heard of that site. I will check it out. |
| 19:04 | <Seirdy> | it's like a POSIX manpage i guess. |
| 19:05 | <Seirdy> | in certain respects |
| 19:05 | <Andreu Botella> | Thanks, Andreu. This is the first I've heard of that site. I will check it out. |
| 19:27 | <Andreu Botella> | I was checking something in the images part of the spec, and I noticed that images can be fetched on demand (https://html.spec.whatwg.org/multipage/images.html#when-to-obtain-images), which sounds like it should be the same as lazy-loading |
| 19:27 | <Andreu Botella> | But lazy loading is disabled if scripting is disabled because of tracking concerns, while fetching images on demand isn't: https://html.spec.whatwg.org/multipage/urls-and-fetching.html#will-lazy-load-element-steps |
| 21:28 | <zcorpan> | Andreu Botella: on demand means that it's not loaded until the user asks for it to be loaded (via context menu or so) |
| 21:31 | <Andreu Botella> | oh, right, that makes a lot more sense |