[TYPO3] Google Chrome Browser

[Andrew Plank]

Rudy Gnodde wrote:
> It doesn't happen everywhere in the backend. It only seems to happen 
> when editing an item (like a content element). Safari doesn't have this 
> problem, so that would suggest it's not a Webkit thing, but something in 
> Chrome's JavaScript engine.

Interesting indeed! Hopefully they'll sort that out. And hopefully 
they'll add a bunch of configuration options - it's very sparse atm.


<ot>
Anyone know where the equivalent of about:config is?
</ot>