[TYPO3-core] RFC #14348: Fix some link targets in the Install Tool

[Lars Houmark]

Hi Patrick,

Patrick Broens wrote:
>> So, do you have some JS code (which you used before) to accomplish this?
> Try this:
> <a href="page.html" class="new-window">Page</a>
>
> window.onload = function() {
>      var links = document.getElementsByTagName('a');
>      for (var i=0;i<  links.length;i++) {
>          if (links[i].className == 'new-window') {
>              links[i].onclick = function() {
>                  window.open(this.href);
>                  return false;
>              };
>          }
>      }
> };
>
> or using jQuery which could be changed to extJS:
> $(function(){
>      $('a.new-window').click(function(){
>          window.open(this.href);
>          return false;
>      });
> });
>>> Please keep W3C validation in mind, especially now we started the
>>> Backend Cleanup Project.
>> And with that I can only respond; Please keep a working (and user
>> friendly) TYPO3 installation in mind.

He he, the Install Tool already uses Prototype. Let's clutter the tool 
with another 50k+ library in order to make it happen. One that might 
conflict with Prototype and break current functionality (for creating 
the pretty important encryptionKey). And I am not saying using Prototype 
over jQuery or ExtJS is better (I don't like prototype in general) but 
that is "what we got at this point" so we need to stay compatible with that.

I am 100% against doing something this simple this advanced and 
unnecessary, when I can see no reason for having the strict doctype, so:

1) Can you argue more concrete for using the strict doctype, besides a 
"more clean markup" that for a backend with some special needs only will 
create extra code like the one you just created.

2) Let's have the RM or CL in here and decide what should be the ongoing 
method. I mean, there is already several votes for using the more 
"flexible" doctype and then one against, which I until now I cannot read 
any serious arguments for (honestly, strict doctype over a validating 
transitional is not really a big difference for me at this point. I can 
see 100+ other improvements in the backend that ANYONE will gain from 
before that).

I will await for either 1 or 2 to convince me, before moving ahead on 
this one.

And about the rewritten Install Tool. Maybe it was just rumors or 
misunderstandings, so let's forget about it - it still changes nothing 
of the above.

-- 
Lars Houmark