[Typo3] SOLVED remove onfocus="blurLink(this); from page content menu
Christopher
bedlamhotel at gmail.com
Sun Nov 20 09:20:19 CET 2005
Hi,
On 20/11/05, Matthew Manderson <matthew at manderson.co.uk> wrote:
> LOL
>
> My problem was I COULD NOT include the noBlur within the normal construction
> of the menu because the menu was a page content element created by
> tt_content and NOT as a HMENU / TMENU item in the setup field.
Nevertheless, the object that you added 'noBlur = 1' to was still a TMENU.
> I was having problems trying to find the TYPOSCRIPT 'path' to my page
> content elements.
>
> I think this javascript rubbish should be off by default and turned on if
> you fancy it. Exactly as it says in TSREF.
I guess this is unlikely to happen soon--backwards compatibility...
> This means that to turn it off you need to find it manually in the object
> tree.
Yep. Convenient, no?
> What happens now if a site editor adds a nice fancy page content menu to the
> site? The JS will raise its ugly head again. Someone will complain ie6 is
> messing up for them with JS errors and I will be called in to fix a
> 'broken' website.
Well, there are a finite number of types of menus available by
default. Add the 'noBlur = 1' property to all of them. Should take
about 5 minutes to do.
> Does anyone know where the TSREF is that explains how the '20.default' and
> '20.4' relate to my setup?
Nowhere. But click your way through menu options in the TS object
browser; you'll see that the objects you're changing _are_ TMENUs.
This is the genius of how Typo3 renders content; just about _all_ of
Typo3's output is based on TS objects. This means that if you
understand the basic set of TS objects--which _are_ documented in the
TSref--you have almost complete control over how any given type of
content gets rendered.
Moreover, since the defaults can be defined by extensions (I'd guess
you are using the CSS Styled Content extension), you can write your
own extension to either a) take over content rendering completely (big
job!) or b) change only the aggravating features of the default
content rendering to suit your needs.
-Christopher
More information about the TYPO3-english
mailing list