| 07:32 | <wfpkhc> | why does - https://html.spec.whatwg.org/#the-input-element |
| 07:32 | <wfpkhc> | have "alt" attribute - |
| 07:34 | <wfpkhc> | if you have an <input type="text" |
| 07:34 | <wfpkhc> | then you are not going to use an alt tag |
| 07:34 | <wfpkhc> | https://html.spec.whatwg.org/#text-(type=text)-state-and-search-state-(type=search) |
| 07:34 | <wfpkhc> | does not specify only which attribute applies to this version of an input |
| 07:35 | wfpkhc | sits quietly |
| 07:38 | wfpkhc | waves bye bye to yudai |
| 07:38 | <wfpkhc> | i hope he comes bakc |
| 07:38 | <wfpkhc> | back |
| 07:38 | wfpkhc | waves hello to Yudai |
| 07:38 | <wfpkhc> | welcome back |
| 07:39 | wfpkhc | sits quietly while waiting for a response... |
| 07:42 | <wfpkhc> | what im trying to get is a complete list of global attributes for <input> |
| 07:42 | <wfpkhc> | but the document specifies it for all inputs |
| 07:42 | <wfpkhc> | what would be interested is to have an section for <input type="text" (or any other input type) |
| 07:44 | wfpkhc | feels alone* |
| 07:49 | wfpkhc | waves bye to goplat* |
| 07:49 | <wfpkhc> | i wonder if he will come back... |
| 07:59 | wfpkhc | sits and waits quietly |
| 08:22 | <wfpkhc> | HMM |
| 08:22 | <wfpkhc> | did find a table with certain aspects on that web page |
| 08:23 | wfpkhc | waves hello to belolap |
| 08:23 | <wfpkhc> | i guess not |
| 08:31 | <wfpkhc> | i think that the documenation is missing somethin |
| 08:31 | <wfpkhc> | https://html.spec.whatwg.org/#the-input-element |
| 08:31 | <wfpkhc> | this table is missing the "disable" attribute on the table for the input types |
| 08:31 | <wfpkhc> | welcome back |
| 08:32 | wfpkhc | sits quietly |
| 08:41 | wfpkhc | looks around |
| 08:41 | wfpkhc | yawns |
| 08:47 | wfpkhc | still here |
| 08:54 | <wfpkhc> | welcome back belolap |
| 09:10 | <wfpkhc> | hello |
| 09:10 | wfpkhc | sighs and sits quitly waiting for someone* |
| 09:12 | <rianby64> | hello! I've a question about the example at https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-data-element I know that the examples are not so important, but I'd like to know if the <script src="sortable.js"></script> element should be there or not |
| 09:13 | <rianby64> | I ask because I don't see the code for that script, and I consider it's not necessary to include it in the example... |
| 09:19 | <Zegnat> | I am guessing it is included to make it clear that the extra data provided by the data elements is not consumed by most useragents (e.g. browsers), but the author will have to include scripts themselves. A table sorting script makes for a pretty clear example. |
| 09:19 | <wfpkhc> | hello rianby64 |
| 09:20 | <wfpkhc> | wtf! how come he messages someone and ges a response and i have been here an hour or more |
| 09:20 | wfpkhc | ponders if he is invisible |
| 09:21 | <Zegnat> | I just happened to scroll by. |
| 09:21 | <wfpkhc> | lucky him |
| 09:21 | wfpkhc | sits and pouts on the couch* |
| 09:22 | <rianby64> | ah, uh, ok. Thanks Zegnat. |
| 09:23 | <wfpkhc> | sooooooooo |
| 09:23 | <Zegnat> | wfpkhc, I believe alt is available on input elements because of type="image" not having any other way to enable UAs to read them out |
| 09:23 | <wfpkhc> | yes its available on type image - i get that |
| 09:23 | <wfpkhc> | what i dont get - is why is it on the type text? |
| 09:24 | <Zegnat> | Is it? |
| 09:24 | <wfpkhc> | according to the documentation it is |
| 09:24 | <wfpkhc> | https://www.w3.org/TR/html51/sec-forms.html#the-input-element |
| 09:24 | <Zegnat> | If you look at the table listing what attributes are in effect on what types it is only listed for type="image" |
| 09:25 | <wfpkhc> | but the table is missing information |
| 09:25 | <wfpkhc> | its missing the "disabled" attribute |
| 09:26 | <Zegnat> | Note the sentence “Which of the accept, alt, […] step, and width content attributes, […] IDL attributes, […] methods, and […] events apply to an input element depends on the state of its type attribute.” |
| 09:27 | <Zegnat> | The table is actually a “non-normative” summary. I am not 100% sure where the formal attributes-per-type is defined. |
| 09:28 | <wfpkhc> | k |
| 09:29 | <Zegnat> | https://www.w3.org/TR/html51/sec-forms.html#element-statedef-input-text - scroll down to “bookkeeping details”, you will see alt is not a listed attribute for type="text" |
| 09:29 | <Zegnat> | A comparable section should be included for every type state. |
| 09:30 | <Zegnat> | I hope that gets you going, wfpkhc :) |
| 09:30 | <wfpkhc> | thank you sir but i was told this list was better then w3 |
| 09:30 | <wfpkhc> | w3c |
| 09:32 | <wfpkhc> | but appreciate the link sir |
| 09:32 | <Zegnat> | The same definition is available on the whatwg version |
| 09:32 | <Zegnat> | https://html.spec.whatwg.org/#text-(type=text)-state-and-search-state-(type=search) |
| 09:32 | <Zegnat> | Scroll down to bookkeeping |
| 09:33 | <wfpkhc> | k sir |
| 09:34 | <Zegnat> | So, yeah, there is a list per input type. Hope that does answer your initial question. |
| 09:34 | <wfpkhc> | to be honest sir its 7 30 pm |
| 09:35 | <wfpkhc> | im dog tired and can barely read the screen |
| 09:35 | <wfpkhc> | i think its about time i signed of shortly |
| 09:37 | <wfpkhc> | thank you Zegnat |
| 09:37 | wfpkhc | hung smaug and gives him a gold coin as i know he loves gold under the mountain* |
| 09:39 | <wfpkhc> | *hung = hugs* |
| 09:39 | <wfpkhc> | lol im a little tired |
| 09:39 | <wfpkhc> | and read what i just said :P |
| 09:39 | <wfpkhc> | hello foolip |
| 09:41 | <foolip> | hello wfpkhc :) |
| 09:41 | <wfpkhc> | how are you sir? |
| 09:41 | <foolip> | wfpkhc: doin OK, had a bit of fun with https://stackoverflow.com/questions/16037787/convert-mercurial-project-to-git |
| 09:42 | <wfpkhc> | thats awesome - i have no idea of what you are talking about but im happy for you |
| 09:44 | <foolip> | anyone want to review https://github.com/w3c/web-platform-tests/pull/6302 for me? annevk? |
| 09:45 | <wfpkhc> | what is it? |
| 09:45 | <foolip> | wfpkhc: tests for the fullscreen API when you remove an element which is in fullscreen |
| 09:46 | <wfpkhc> | oh ok |
| 09:46 | <wfpkhc> | clearly outside my realm of understanding |
| 09:55 | <wfpkhc> | night night all |
| 09:55 | <wfpkhc> | my brain has stopped working after 14 hours of programming |
| 09:55 | <wfpkhc> | bye |
| 11:12 | <smaug> | CEReactions handling in specs is error prone |
| 11:13 | <smaug> | I guess also in implementations |
| 11:13 | <smaug> | how can we guarantee it is used whenever needed |
| 12:05 | <GPHemsley> | that person is starting to bother me |
| 12:06 | <GPHemsley> | we've determined now that they're in UTC+10, at least |
| 12:12 | <nox> | GPHemsley: Grepped their handle on botbot.me, was not disappointed. |
| 12:16 | <GPHemsley> | nox: I suppose you'll have to define "not disappointed" for me >_> |
| 12:17 | <nox> | I have weird tastes when it comes to entertainment. |
| 14:06 | <annevk> | smaug: for CEReactions the alternative would be to always run those steps instead of only when annotated with CEReactions, but the feedback from implementers was to have the optimization defined in the specification as it would be more likely to be correct and aligned across implementations that way |
| 14:41 | <smaug> | annevk: sure. I just wonder how to make the setup less error prone |
| 21:21 | <TabAtkins> | If I can catch them next time they're on I'm going to inform them of general etiquette, otherwise I'm just /ignore'ing them. |
| 23:18 | <Shalom> | exit |