Bug #63139
closedPagetree does not jump to unfolded page when creating internal link
0%
Description
When creating an internal link and unfolding a page in the pagetree, the pagetree reloads but no longer jumps to the page the editor just unfolded. The editor has to scroll down to find the page again.
This is particularly annoying on large sites where you have to unfold many pages to find the target page.
Updated by Bryan Dijksterhuis over 9 years ago
Bart Gijswijt wrote:
When creating an internal link and unfolding a page in the pagetree, the pagetree reloads but no longer jumps to the page the editor just unfolded. The editor has to scroll down to find the page again.
This is particularly annoying on large sites where you have to unfold many pages to find the target page.
A client of my company also found this bug. After looking around I managed to find out it is caused in the file "class.browse_links.php" in the typo3_src/typo3/ folder. The line at which the bug occurs is 115. The original code shows:
$name = ' name="' . $bMark . '"';
Note the double quotes around the $bMark variable. A couple of lines later this $name variable is inserted into the <a> tag with the htmlspecialchars function surrounding it:
return '<a href="#"' . htmlspecialchars($name) . ' onclick="' . htmlspecialchars($aOnClick) . '">' . $icon . '</a>';
This is where the bug occurs. Somehow htmlspecialchars seems to add an extra set of double quotes around the, already existing, double quotes that surround the $bMark variable. If I remove the existing double quotes around the $bMark variable like below, and save the file and try again, then the jumping-to-opened-page works exactly like expected.
TL;DR: class.browse_links.php adds redundant double quotes on line 115 which means the value of the name tag doesn't match the value set in the onclick action.
This was tested on a TYPO3 6.2.9.
If you need more information, let me know and I'll see what I can do for you :)
Sincerely yours,
Bryan Dijksterhuis
Youwe
Updated by Wouter Wolters over 9 years ago
- Status changed from New to Closed
yes this has been fixed with #66854