| 15:41 | <qFox> | hey. what's the proper term for a javascript: url and where can i find specs for that? |
| 15:45 | <Ms2ger> | In the HTML spec, navigation section |
| 16:00 | <qFox> | i guess here https://w3c.github.io/html/browsers.html#navigating-across-documents , thanks :) |
| 16:01 | <Ms2ger> | Nonono |
| 16:01 | <Ms2ger> | https://html.spec.whatwg.org/multipage/browsers.html#javascript-protocol |
| 16:01 | <Ms2ger> | W3C's fork of HTML is notoriously low-quality |
| 16:05 | <qFox> | ah, sorry for cursing :) |
| 16:08 | <qFox> | a little confusing in both specs (which say nearly the same thing); that spec mentions explicitly what happens when the result is not a string. yet in the example below it it explicitly mentions that "its return value (if it was not void) would replace that browsing context's Document". |
| 16:09 | <qFox> | this kind of implies (and only through the example) that an undefined result, triggers a status code 204 but does not throw away the current browsing context. is that correct? |
| 16:11 | <Ms2ger> | The example is probably wrong |
| 16:11 | <Ms2ger> | The check for being a string was changed recently? |
| 16:12 | <Ms2ger> | https://github.com/whatwg/html/issues/1415 |
| 16:12 | <qFox> | ok. so what _should_ happen for undefined results? |
| 16:13 | <qFox> | (another reading could be that "void" in the example refers to a spec artifact rather than the actual JS value "undefined"...) |
| 16:14 | <qFox> | the reason that actually drew me here was what the context should be that these urls should run in. when you do `javascript:this.x=5,'<script>console.log(this.x);</script>'; what should happen? for example; firefox says it works, chrome says it doesnt |
| 16:15 | <qFox> | *when it's the url of an iframe... |
| 16:17 | <Ms2ger> | File an issue? I think it's known, but I can't find an open issue |
| 17:01 | <Ms2ger> | TabAtkins, thanks, you're a gentleman and a scholar |