Title

I got unstuck on the cursor issue I was having, so onward to new work! Which means I have some questions about what people expect behavior to be like.

1) If you have your cursor somewhere in a document, with no text selected, and you use either the toolbar button or keyboard shortcut to toggle a block element (like a blockquote or header), what do you expect to happen?

2) If you are inside a block element (like a blockquote or bulleted list), how do you expect to be able to exit the block element and resume writing 'normal' text?

(I also got unstuck on the AO3 Kobo reader, once I remembered how to build the package properly, but I'm going to work on Lolibrary search stuff today, I think)

Now actually on my dev environment here (link will let you work as one of my dev testing accounts, rather than having to register a new one). We now have real image uploading! And partial cut tag support!

To-dos for this -
Editor functionality:
- Add font-size options
- Editing view for cut text/usernames
- alt/title updates for images
- sort out wonkiness with cut creation
- sort out p versus br/inline vs block issues, ugggggh
- clean up event handling

Look and Feel
- image upload button should be disabled for non-logged-in users
- styling to match site schemes
- figure out nicest way to collapse sections on small views/tackle 'so many toolbar buttons'
- selection styling
- button icons (currently using fontawesome for ease of use, but I don't really want to ship a whole webfont for like ten icons)
- display for error messages

Wiring
- selector to swap between RTE and html modes
- parsing for pre-existing entries into RTE editor (related to inline vs block issues, sigh)
- deleting images in the editor should also delete them from storage

Post-Beta
- Poll-creator rewrite, bleh
- Replacing the JS prompts with actual modals
- Keyboard shortcut doc


I am super interesting in hearing any feedback people have, both from regular RTE users and non-RTE-users. Not everything on the list above is going to make it in before we get to a production beta, but there's still some very rough/buggy edges which is why this is access-locked for now.