Each Button has a unique URL (just like how each Table and Row has a unique URL). But when you go to the URL in a browser, instead of taking you to a page, the Button becomes Pressed. (Maybe it also takes you to a designated page, too, but that’s less important. If the Button adds a new Row and opening the Row for editing is turned on, then that’s where the browser would take you.)
What would this allow you to do?
Push a button from a browser bookmark bar
Push a button from a phone home page (at least for Android, where you can make a website into a home page icon)
Okay, this is interesting, but I’m not entirely clear how I would use this in practice. At the outset, firing off URLs that act as commands - potentially from a context without authority - is typically not the domain of a browser. Browser’s are designed to only make HTTP GET requests which respond with HTTP content.
To create the possibility of interpreting the URL bar as something more requires a custom protocol. Unsurprisingly, that appears to be what Coda already does with its Chrome Browser Extension.
So, I think what you’re asking for is a custom protocol handler. But, I still want to understand why. If users are able to [manually] click a button or do the same [manually] from an abstracted level in a link, how is that any different (in the case of adding a new row) and not achieved with a URL to a form?
