« Long cache keys make the cache fail.
Input boxes not working in Chrome
Previous/next topics don't work properly »

Nao

  • Dadman with a boy
  • Posts: 16,082
Input boxes not working in Chrome
« on January 25th, 2013, 10:44 AM »
This happened to me twice -- yesterday, and this morning. Both times, it didn't happen at startup, only after a while.

Suddenly, in Chrome, all text inputs in Wedge would stop working. Cursor shows up, but typing doesn't add anything to them.
It only works in the Search Box. Removing (with the dev tools) the search class from it did at some point block input, restoring the class restored input, but this didn't 'fix' other text inputs. Also, removing the search class a second time didn't seem to break functionality again.

Just like the previous bug I reported -- it's very random. But if it's happened to me twice... And it can't be fixed by closing and reopening the tab, only by closing Chrome... I'm guessing I should report.

This is with version 26 (Chrome Canary).
Re: Input boxes not working in Chrome
« Reply #1, on January 25th, 2013, 03:02 PM »
Hmmm... Very very odd.
Open quick reply, no can write, click the arrow, can write (contenteditable = good.)
Click the arrow (to textarea), can keep writing *apparently*. I'm saying 'apparently' because it doesn't actually restore the textarea (the outline color not changing in Chrome is a hint... And it's buggy everywhere at this point, like clicking smileys won't add them, etc.)
Click the arrow (to div), the text is replaced by whatever was in the div before I made the 'wrong' click... EH??!?!!*#$!!!
First time this ever happens to me... Dunno if it's related to the bug above, probably is.

It's quite f'ed up if I must say...

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Input boxes not working in Chrome
« Reply #4, on January 25th, 2013, 07:03 PM »
Bug reproduced three times... (Three restarts.)

And DEFINITELY a Chrome bug.

You know what fixed it...?

Removing the :focus and :hover border in select/textarea/input.
This is incredible.
And I have no frigging idea why it would work when applying background/padding-left/height elements to the same stuff (e.g. input.search), but I don't even want to know. Chrome can do without the focus border, really! It's just a nice detail... And it has the outline anyway.
Re: Input boxes not working in Chrome
« Reply #5, on January 29th, 2013, 10:50 AM »
What should we do next for this?
I committed the fix yesterday, but I don't know if it's worth keeping it in forever.
1/ Chrome might fix the bug at some point... (I don't want to have Wedge keep fixes forever, just look at the state of the SMF codebase, full of IE4 fixes and all! Especially their JS scripts!)
2/ It doesn't happen all the time, and if I can't reproduce consistently, I can hardly quickly know when this is fixed... :(

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Input boxes not working in Chrome
« Reply #6, on January 29th, 2013, 01:51 PM »
Keep it for now, and if Chrome fixes it, let's remove it. I guess we'll just have to retest it thoroughly in about 6 weeks.

Nao

  • Dadman with a boy
  • Posts: 16,082

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278

MultiformeIngegno

  • Posts: 1,337

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Input boxes not working in Chrome
« Reply #10, on January 29th, 2013, 04:52 PM »
Meh, that would require enabling them to reproduce the bug... And I'm pretty sure it's a bitch to reproduce. Unless I re-enable the bug here -- at the cost of my convenience!
« Long cache keys make the cache fail.
Previous/next topics don't work properly »