Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Somewhat hacked together, should better integrate this feature with
Auth.pm but the code is already annoying enough as it is. :(
|
|
|
|
|
|
With filters and all. Mostly for moderation purposes.
|
|
With a better listing, submissions form, moderation interface and
voting.
|
|
|
|
Pointless busywork, because my brain is too mushy to work on useful
stuff. :(
|
|
Turns out it's "エルエル" (capitalized as either Elel or ELEL, not
sure), based on https://vndb.org/t16934.14 & https://vndb.org/t950.1667
|
|
|
|
No major changes compared to the Elm version, just a few minor
improvements:
- Better error reporting of invalid URLs
- Language field does not have a default anymore
- Duplicate staff list also displays alttitle
- Allow romanization for Greek names
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unfinished, primarily for testing.
https://vndb.org/t20399.36
|
|
|
|
These nested boxes kinda looked messy.
|
|
|
|
https://vndb.org/t8242.1481 onwards
|
|
A compromise between https://vndb.org/t20601.25 and https://vndb.org/t20601.26
|
|
In particular, this ensures that only the nested box is scrolled and
never the whole page. Also fixes scrolling behavior on PaleMoon.
|
|
Had to add a wrapper <div> for the results, because column layout and
max-width don't work on a single element. Putting a height:100% on the
<ul> appears to do the trick.
|
|
Main problems I ran into:
- Not all browsers (especially true for mobile browsers) support
reportValidity(), so we need custom reporting anyway.
- Some browsers (or addons, dunno) completely ignore form validation and
pretend everything is valid; those users will not have a very good
experience.
- setCustomValidity() only works on 'willValidate' form elements, which
means we need additional custom reporting for errors that do not apply
to such elements.
- 'minlength' doesn't work at all when the input's value is set by JS.
- Getting reportValidity() to work with FormTabs was extremely awkward.
Sad, because the idea of offloading form validation and reporting to the
browser is actually a pretty useful idea.
Anyway, this custom implementation should be more robust. Also provides
much better feedback on invalid usernames.
|
|
- The "Erase" button thing on the engine & resolution dropdowns didn't
seem very easy to discover, better just add "Empty" as an explicit
option.
- Auto-add valid URLs in the external links thingy and disallow form
submission if the field is not empty.
- Check for duplicate media
- Check for missing VN relations
- Update romanization field check to be in line with
f50d1692262ea0dcc60e0f61d05a0a5c63528604
- Some CSS fixes
|
|
This completes the form, but I rushed it a bit so there's bound to be
some issues left.
|
|
Straightforward Elm to JS port, no real changes otherwise.
|
|
I'm not sold on the validity API at all.
|
|
|
|
As discussed in https://vndb.org/t20453
|
|
So that the save/load functionality is also available on a user's list.
Suggested by https://vndb.org/t950.1537
|
|
As suggested by https://vndb.org/t950.1532
|
|
Main reason for this rewrite is that I realized that many mobile
browsers don't properly support reportValidity() yet. The new form code
still heavily uses the HTML5 validation API, but doesn't rely on
reportValidity() as much since it has CSS :invalid fallbacks. And even
if that fails, the error messages reported by the server are slightly
more useful.
Also removed the bot verification question as an experiment, might come
back if it turns out to be needed.
Also added a silly checkbox to check if people read checkbox labels.
Also used <input type="email"> to help mobile browsers select the right
keyboard.
|
|
|
|
Adding help text to forms is something I've been wanting to do for quite
a while, but I could never decide on the how nor get over how annoying it
would be to implement in Elm. I now have something that could work.
Simple does it \o/
|
|
Because the new check/radio styling overrides some visuallyhidden
properties and causes the page to scroll when clicking a linkradio
thingy. Not sure the "visuallyhidden" hack ever helped anyone.
|
|
from v2.css
|
|
Amazing how that arrow improves usability. Feeling a little better about
the click-to-open-dropdown thing now.
|
|
This one was fairly simple, with all the infrastructure already in
place. Not the biggest fan of the placement of that intro text though,
and the table styling can be improved, but w/e.
|
|
|
|
Multiselection thingy was easier than I expected, but the UI doesn't
feel quite right somehow. :/
|
|
tweaking
|
|
Not yet super happy with the table-in-form layout thingy; buttons jump
around when adding/removing items, ugh.
I *am* quite happy with the dropdown search thingy, the new features
make it much more intuitive to have items that can't be selected. The
current Elm code usually ignores the selection of items that are already
present or otherwise unselectable, which can be rather confusing.
Having the input field replaced with a button is something I'm not yet
decided on. It does makes sense, but also requires an additional action
when adding multiple traits. Even if that action is just pressing the
enter key. Multi-select built into the DS abstraction might be a
solution.
|
|
Trying to go all-in on HTML5 validation. It's very quirky, not sure
how well this will work out, but so far it's kind of working.
|