| 00:01 | <heycam> | zewt, I'm working on getting text selectable in Firefox, should land in a couple of weeks |
| 00:02 | <zewt> | looks like it's selectable in chrome, but still doesn't highlight on search |
| 00:02 | <zewt> | (which seems odd--seems like the hard part's done) |
| 00:03 | <heycam> | (https://bugzilla.mozilla.org/show_bug.cgi?id=655877 if you care) |
| 01:16 | <TabAtkins> | Hixie: Good point about the normal case being straight line. In that case, <optional> should be a leaf node, and <choice> can put its first option in the straight line position. |
| 01:17 | <Hixie> | fair enough |
| 01:17 | <TabAtkins> | I *think* you can write the def_param_list without repeating yourself. I'll see. |
| 01:17 | <TabAtkins> | And yes, I just haven't needed a <sequence> element yet in those two examples (assuming that there's implicit sequencing at the root). |
| 01:18 | <TabAtkins> | So far, I'm just planning on using this for the CSS token syntax. If it's useful for other stuff in the future, that's cool. ^_^ |
| 01:19 | <Hixie> | cool |
| 01:36 | <TabAtkins> | Ugh, the def_param_list *is* doable in my syntax without repetition, but you have to rewrite it to be less clear (so all the skips are cleanly nested). |
| 01:36 | <TabAtkins> | Oh well, I can always manually generate things that run into that kind of problem. |
| 01:36 | <TabAtkins> | To be fair, this grammar is actually kinda hard to write as a regex or BNF. |
| 01:37 | <TabAtkins> | Or, no, a BNF for it is probably pretty easy. |
| 01:37 | <TabAtkins> | My syntax works well for regex-style things only. |
| 01:38 | <TabAtkins> | But being able to generate *most* of that diagram (everything but the skip line at the bottom) automatically and just hand-filling in the last bit is still pretty good. |
| 01:41 | <Hixie> | yeah, that's certainly a good start :-) |
| 01:42 | <Hixie> | dunno how often one would see that anyway |
| 18:56 | <GPHemsley> | Hixie: Does this (really old) bug relate to the unload stuff you were working on the other day? https://bugzilla.mozilla.org/show_bug.cgi?id=13701 |
| 18:56 | <GPHemsley> | (Oh, you were the QA Contact on it until 2009!) |
| 18:59 | <GPHemsley> | Is there a document describing what "DOM0" actually refers to? Or is it just some arbitrary name for "whatever browsers supported as of XYZ date"? |
| 19:01 | <GPHemsley> | And are the features of DOM0 superseded by other documents? Or do the other DOM documents build orthogonal to each other? |
| 19:04 | <zewt> | DOM0-kun? |
| 19:04 | <GPHemsley> | ? |
| 21:04 | <annevk> | GPHemsley: DOM0 are the APIs not in the DOM or JavaScript before HTML and related efforts standardized most of them |
| 21:04 | <annevk> | if that makes sense |
| 21:05 | <annevk> | e.g. window, window.history, window.location, XMLHttpRequest, keyboard events |