Opera updated to 10, but now when one goes to edit the tags, the starting place is at the end of the current tags, instead of at the start, like it had been. This makes adding tags a bit awkward, at least with being so used to before, since now forgetting to hit space before adding anything can give ya doubled-up tags.
I caught my last/latest goof-up, but unfortunately didn't get the box reselected before hitting space, which apparently acts like Enter when one's tabbed onto the Save changes button.
It's always been like this in Firefox. It's probably doing what it was intended to now. I actually prefer it start at the end, but an ideal solution would be to start at the end and automatically insert a space.
Oh, come on. It's a text box. This modification is something that belongs in a greasemonkey script, if anywhere. Such tiny UI details as "where in the text box the cursor should be initially placed" do not belong in the server-side implementation. In fact the concept of a "cursor" doesn't even necessarily exist in all browser implementations.
hmm. It's not suppose to start at the end of the last tag? I used FF2 and FF3. So it has always been like that... sometimes I just copy paste a stack of tags, and everything ends up fine.
0xCCBA696 said: Oh, come on. It's a text box. This modification is something that belongs in a greasemonkey script, if anywhere. Such tiny UI details as "where in the text box the cursor should be initially placed" do not belong in the server-side implementation.
Why's that? There are actually a couple text boxes where I wish the cursor would appear by default when you load the page as well. Like, say, the search box on http://danbooru.donmai.us/post/index
It seems fairly common for websites to do this sort of thing by default, without user scripting.
jxh2154 said: Why's that? There are actually a couple text boxes where I wish the cursor would appear by default when you load the page as well. Like, say, the search box on http://danbooru.donmai.us/post/index
It seems fairly common for websites to do this sort of thing by default, without user scripting.
That's a pretty big detail actually. Not saying its a bad idea but its the kind of thing that would affect everyone instead of the original problem described here (an outdated version of an inferior browser messing with the site).
jxh2154: Well, that's a bit different. There is a concept of "focus" in the DOM which can be used to focus certain controls on the page, such as text-boxes. But how the actual input into those controls is handled should be up to the individual browser implementation. That way if a page were rendered in, say, an audio-only browser, where there was no concept of a "cursor editing" system for text-boxes, only a "input and start over until satisfied" system, it wouldn't make sense. I don't think there even is a way to do that with Javascript, actually.
