# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 12
# self = https://watcher.sour.is/conv/7nfewkq
TIL: that the <button> element in HTML5 will cause a form to submit when clicked (instead of any other behaviour you expect) because <button> has a default value of, get this... type="submit".
You would think <button> would have a default type of "button", but no. Bloody hell lol.
This Stackoverflow answer saved me from further headaches.
@eldersnake a button having a default type of “button”?! That’s insanity!!!! What next, <a> having the default behaviour of a link?! /s
At least it’s good to know that buttons have a default type of submit, even if it’s a dumb decision
@eldersnake Is it because there are no other buttons in the form? 🤔
@eldersnake Is it because there are no other buttons in the form? 🤔
@eldersnake Is it because there are no other buttons in the form? 🤔
@eldersnake Is it because there are no other buttons in the form? 🤔
@prologic Surprisingly no. In my case I already a regular <input type="submit"> in the form. It's just the HTML5 spec, for some reason, that if a button has no type explicitly defined, it defaults to type="submit" LOL 😅
@prologic Surprisingly no. In my case I already had a regular <input type="submit"> in the form. It's just the HTML5 spec, for some reason, that if a button has no type explicitly defined, it defaults to type="submit" LOL 😅