| 15:28 | <bkardell> | totally random q.... would it be useful for anyone else if the HTML spec had a service worker / offline ? Has someone made a fork like that or something? Was it discussed? |
| 15:29 | <bkardell> | I feel like I open this doc for searching very often and it generally takes a long time to load - if my connection just happens to be slow atm it is like... very very slow |
| 15:29 | <bkardell> | I guess I could grab the PDF but ick |
| 15:30 | <bkardell> | fwiw I have given this about 1m thought |
| 15:30 | <Domenic> | It's been discussed and is desired; all the other specs have it. It's just a bit more work nobody has done yet. |
| 15:30 | <Domenic> | The loading time issue is Chrome-specific though. |
| 15:30 | <Domenic> | And a service worker won't help that |
| 15:30 | <Domenic> | It's something about the HTML parser not dealing well with large documents. |
| 15:30 | <bkardell> | ok |
| 15:32 | <bkardell> | It's something about the HTML parser not dealing well with large documents. |
| 15:40 | <bkardell> | never compared in FF before |
| 16:04 | <annevk> | Browsers should just move to daily updates and bundle the HTML Standard |
| 16:05 | <bkardell> | :) |
| 16:15 | <jgraham> | Although if he problem is HTML parsing, they'd need to bundle some kind of dump of the internal representation. |
| 16:15 | <jgraham> | Might be easier for Chrome to just bundle gecko and use it for that URL ;p |