| 01:01 | <KevinMarks> | Do you still use .ico? |
| 01:03 | <MikeSmith> | JonathanNeal: http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0180.html |
| 01:04 | <MikeSmith> | KevinMarks: ↑☃ |
| 01:06 | <KevinMarks> | Hm so I need to join that mailing list to talk about fragmentions? |
| 01:06 | KevinMarks | is seeing lots of very cumbersome linking models |
| 01:08 | <MikeSmith> | KevinMarks: you can subscribe to the list but there's not much talk about fragmentions on there at this point |
| 01:09 | <KevinMarks> | I was going to bring it up on whatwg once we had it working in practice for a bit |
| 01:09 | <MikeSmith> | yeah whatwg list always works |
| 01:10 | <MikeSmith> | KevinMarks: I was just pointing that out as a data point about potential standardization movement in this area |
| 01:10 | <KevinMarks> | Yes, I was at the w3c annotation meeting, that was what set me off thinking about it |
| 01:10 | <MikeSmith> | shepazu driving that, as far as W3C goes |
| 01:10 | <MikeSmith> | KevinMarks: ah ok |
| 01:12 | <KevinMarks> | But they seem to be doing the gigantic satisfy all use cases with lashings of rdf in three years type WG |
| 01:16 | <MikeSmith> | KevinMarks: yeah that's part of the W3C tax |
| 01:16 | <MikeSmith> | that's hard to avoid sometimes when trying to get work done at the W3C |
| 01:16 | <MikeSmith> | but I think shepazu is savvy enough to know how to contain it |
| 01:16 | <MikeSmith> | mitigate the costs |
| 01:17 | <MikeSmith> | anyway, I think we could specify the addressing stuff just in the webapps wg |
| 01:18 | <MikeSmith> | which is one relatively non-pathological WG at W3C |
| 01:18 | <MikeSmith> | and free from the RDF disease |
| 02:59 | <JonathanNeal> | Great, I hope we can get Doug’s feedback on fragmentions. |
| 02:59 | <JonathanNeal> | Thanks for sharing, MikeSmith |
| 04:08 | <SamB> | hmm, the Status on http://www.whatwg.org/specs/web-controls/current-work/ seems kind of innacurate ... |
| 10:26 | <JakeA> | Hixie: trying to get Chrome to support the outline algo at the accessibility level https://code.google.com/p/chromium/issues/detail?id=365070#c2 - aware of any previous attempts to do this? |
| 15:10 | <SamB> | huh, SVGDocument has a couple of oddball properties ... |
| 20:01 | <rniwa> | Ms2ger: hi Ms2ger! |
| 20:02 | <Ms2ger> | Uh oh |
| 20:05 | <Ms2ger> | rniwa, what's up? |
| 20:06 | <rniwa> | Ms2ger: nah, just saying hi |
| 20:06 | <rniwa> | othermaciej: hi othermaciej! |
| 20:07 | <othermaciej> | hello rniwa! |
| 20:07 | <rniwa> | Ms2ger: we should talk about what to do with innerText at some point though... |
| 20:07 | <Ms2ger> | My position is still "not going to implement in Gecko or Servo" :) |
| 20:08 | <rniwa> | othermaciej: lol |
| 20:08 | <rniwa> | Ms2ger: ^ |
| 20:08 | <Ms2ger> | Unless you get google.com to depend on it, I guess :) |
| 20:08 | <rniwa> | Ms2ger: I do think innerText is a useful feature though |
| 20:09 | <Ms2ger> | That'll depend on which implementation of it you mean :) |
| 20:09 | <Ms2ger> | s/<br>/\n/ doesn't seem too useful, and going full CSS... Not sure that's worth the complexity |
| 20:10 | <rniwa> | Ms2ger: going full CSS of course |
| 20:10 | <othermaciej> | Ms2ger: plaintext conversion is a useful feature |
| 20:10 | <rniwa> | Ms2ger: i agree s/<br>/\n/ won’t be useful |
| 20:10 | <othermaciej> | Ms2ger: you could debate whether innerText is the best way to expose it |
| 20:10 | <othermaciej> | Ms2ger: but it doesn’t otherwise exist in the platform |
| 20:11 | <othermaciej> | I feel like exposing what you do when you paste as plaintext (e.g. “Paste and Match Style” on Mac) is useful |
| 20:11 | <Ms2ger> | I'm not denying it could be useful, just not sure if it's worth the cost, personally |
| 20:11 | <othermaciej> | you could argue that you can only get that conversion as a side effect of a user-initiated paste, but that seems against the Extensible Web Manifesto |
| 20:12 | <othermaciej> | well, at least for Mac browsers, it’s functionality that needs to exist anyway |
| 20:12 | <Ms2ger> | Also, not sure if all consumers would be happy with the exact same functionality |
| 20:12 | <othermaciej> | the only question is whether to give it explicit API surface |
| 20:12 | <othermaciej> | I am not sufficiently familiar with Windows to know if it has the ability to explicitly paste as plaintext |
| 20:13 | <rniwa> | Ms2ger: I definitely agree with the complexity argument |
| 20:13 | <othermaciej> | I know the native Mail client on Mac has “convert to plaintext”, as does the text editor |
| 20:13 | <othermaciej> | it might be that web apps offering equivalent functionality prefer to do it by hand |
| 20:13 | <rniwa> | Ms2ger: if Servo can get away with not having innerText, maybe we just need to leave it up to UA to implement in accordance with the host platform |
| 20:13 | <othermaciej> | is the complexity about implementation or spec? |
| 20:13 | <rniwa> | othermaciej: perhaps we need some API to help that? |
| 20:14 | <Ms2ger> | If Gecko can get away with it now, I don't know why Servo wouldn't be able to :) |
| 20:14 | <rniwa> | othermaciej: i think implementation & spec. |
| 20:15 | <Ms2ger> | And testing and attack surface, as usual |
| 20:16 | <othermaciej> | I was going to say Gecko on Mac doesn’t seem to support Paste and Match Style |
| 20:16 | <othermaciej> | but on the other hand, it seems to only support plaintext paste, even in a contentEditable area |
| 20:16 | <Ms2ger> | (I don't know that feature) |
| 20:17 | <othermaciej> | it can’t even paste styled text from another firefox window |
| 20:18 | <Ms2ger> | It might still be worth doing despite the costs, of course; I'm definitely not going to make that call for Gecko |
| 20:18 | <othermaciej> | only from the same editable area afaict |
| 20:18 | <Ms2ger> | Just don't try to sell it on web-compat :) |
| 20:18 | Ms2ger | is off for a bit |
| 20:20 | <othermaciej> | it would be useful to have data on how many pages as-actually-browsed use it to see if there is really web compat value |
| 23:47 | <KevinMarks> | InnerText is useful for the fragmentions idea. Though collapsing whitespace was handy. |