@slightlylate @LeaVerou The "hard work" is magically intuiting what context an arbitrary string will get used in. That's not possible.
-
-
Replying to @tabatkins
@tabatkins: sooo that seems to imply the design is unclear or not fit for some set of purposes...which implies work to do /cc@LeaVerou2 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@LeaVerou EXACTLY. But it's the design of *relative urls* that's unclear, not the design of URL, which is for absolute urls.1 reply 0 retweets 0 likes -
Replying to @tabatkins
@slightlylate@LeaVerou And this is why we don't (yet) have a "relative URL" interface. It's not super-clear how to make it friendly yet.1 reply 0 retweets 0 likes -
Replying to @tabatkins
@tabatkins: then why isn't the URL parser infra available as a set of methods until then? /cc@LeaVerou1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@LeaVerou What part of URL isn't that?1 reply 0 retweets 0 likes -
Replying to @tabatkins
@tabatkins: Huh? There's a whole relative-state subsection of the parsing algorithm. /cc@LeaVerou1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@LeaVerou Yeah? Do you want to expose a relative url? Then you have to solve the usability issues.1 reply 0 retweets 0 likes -
Replying to @tabatkins
@tabatkins: layered design tends to admit less usability the further down you go. /cc@LeaVerou1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@tabatkins Exactly. Good APIs make the simple easy and the complex possible.2 replies 0 retweets 0 likes
@LeaVerou: in this case there's also a symmetry argument from the <a> parsing hack
/cc @tabatkins
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.