~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+FreefallHeavens
+Over1
+Xeha
+bak83_
+cumlord
+hk
+poriori
+profetikla
+uop23ip
Arch
DeltaOreo
FreeRider
Irc2PGuest19353
Irc2PGuest22478
Irc2PGuest48042
Irc2PGuest64530
Meow
Nausicaa
Onn4l7h
Onn4|7h
T3s|4
acetone_
anon4
anu
boonst
juoQuua9
mareki2pb
not_bob_afk
plap
shiver_1
simprelay
solidx66
thetia
tr
u5657
weko_
zzz
dr|z3d, how do you feel about moving tooltips to placeholders for form text inputs
zzz
and adding more required flags
dr|z3d
zzz: generally speaking, migrating tooltips to form elements, esepcially text inputs, not a great idea.
dr|z3d
adding more required attributes to text inputs, otoh, makes sense. I'm already doing that in +.
zzz
yeah I'm working on i2ptunnel
dr|z3d
you've got 2 issues with placeholder text that are red flags for me.
dr|z3d
firstly, visual clutter. placeholder text might make sense in very limited scenarios like search inputs, for example in snark. but where the entire page is a collection of text inputs, you're just introducing more clutter where you want the least amount possible.
dr|z3d
and secondly, string length will be an issue in i2ptunnel. if the placeholder text is truncated, then fail.
zzz
agreed
zzz
fighting some str4d mess in the wizard
dr|z3d
what's the problem you're attacking?
zzz
hidden inputs between table rows
dr|z3d
that's an easy thing to fix
dr|z3d
you can assign elements to a specific form id and put them anywhere you like, they don't have to be inside the form.
dr|z3d
or, conversely, you can have all your form elements anywhere you want, and the form doesn't have to actually wrap any of them.
dr|z3d
I found the html indentation a nuisance when working on i2ptunnel, so I removed it all. Easier to see where the <%java%> is then.
dr|z3d
if you want the hidden inputs to remain in the html next to the elements they're associated with, that's also easy.
zzz
I'm moving them to the top
dr|z3d
make sure they have the hidden attribute, which they probably already do, and assign a class to them so they don't accidentally get unhidden in the css.
zzz
the nice thing about "required" is that the user gets a translated popup from the browser and we don't have to add a tagged string for it
dr|z3d
well, yes, and no. it's a generic popup, so you can't give the user additional guidance.
zzz
they still have the tooltip
dr|z3d
mozilla did have a custom attribute to add custom text to the required popup, but they deprecated it a while back. you might still have some vestiges of that in the source.
zzz
yes in the css
zzz
moz-placeholder or something
zzz
can i rip that out?
dr|z3d
if you want to get fancy with required, you can use regex to ensure the fields aren't being filled in with dud data.
dr|z3d
you can.
zzz
ok
dr|z3d
but moz-placeholder isn't what I was referring to. that's just moz's prefix for placeholder.
dr|z3d
if you want to support older browsers, then the moz- prefix you may wish to keep. I don't, -moz- and -webkit- are, for the most part, nuked.
zzz
then whats the popup attribute to look for?
dr|z3d
x-moz-errormessage
zzz
nothing in i2ptunnel
dr|z3d
git grep "errormessage" |grep moz
dr|z3d
re -moz- prefixes, my cutoff for support is whatever the Tor browser LTS version is. There was an issue a long time ago where it diverged from normal Firefox in terms of css/html support, but that's no longer the case.
zzz
ok
dr|z3d
I don't know what PaleMoon is doing these days, but that's an edge case where -moz- prefixes may still be required in some contexts.
zzz
I've never really messed with the wizard, it needs a little love, not a lot
dr|z3d
It's pretty good for new users, doesn't attempt to overcomplicate the options.
zzz
yeah I usually forget about it though when making changes on the normal edit pages
dr|z3d
ok, -91+ now available for I2P+ users on the /dev/ update path. informally named "turtle killers".
T3s|4
o/ dr|z3d - running twin turtle killers around these parts ;p
dr|z3d
great, T3s|4, let us know if you encounter any issues. looking good here, no issues to report so far.