[TYPO3-core] RFC #5381: htmlspecialchars and noBlur for tt_content.menu

[Ernesto Baschny [cron IT]]

Susanne Moog wrote: on 18.05.2009 11:57:

>>> Is it possible that the description in TSref is a bit strange?
>>>
>>> Description in TSref is: "If this property is set, the link is NOT
>>> blurred (browser-default) with "onFocus"."
>>>
>>> Now answer: is not blurring or blurring the default behavior?

>> The default of browsers is *not* to blur on focus: that means that on
>> "focus" the link will be highlighted (usually with a dotted border).
>>
>> But IE (since v4) has the annoying feature to also display these dotted
>> outlines when the user "clicks" on a link ("active"): some find that
>> annoying. This is where the "blur" javascript was born. This javascript
>> is added automatically on every menu link (onfocus it "blurs" right
>> away, so avoiding the outline).
>>
>> But this turns out to be very "unaccessible", since it also hides the
>> outline when browsing through the links using the TAB key.
>>
>> So for any accessible site (and as a css_styled_content default) we
>> should not fiddle with the "blurring" on "focus", which is why we need
>> to change the MENU defaults to "noBlur=1". Which is why I wouldn't
>> remove them, but add the one you found out to be missing, Susanne.
>>
>> I think Masi meant that "blur on focus" is bad (the added javascript),
>> and not that "noBlur=1" (not adding the javascript) is bad. Masi?
> 
> If I understood the description right, noBlur = 1 adds the javascript,
> so that would indeed be bad. I have to check what it does - I'll report
> back then.

Hm, not really: noBlur=1 avoids the javascript to be added (good). If it
is not set (or set to =0), the javascript WILL be added (bad).

Cheers,
Ernesto