Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
20 Jun 2008 at 10:31 UTC
Updated:
20 Jan 2016 at 09:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
samirnassar commentedYou should re-roll the patch against HEAD, that is Drupal 7. If you need help making this happen, chime in.
Comment #2
robin monks commentedFree re-roll compliments of patch bingo.
Robin
Comment #4
lilou commentedSee: #335122: Test clean HEAD after every commit and http://pastebin.ca/1258476
Comment #5
catchSeems like a reasonable idea, the last patch has tabs in though.
Comment #6
mattconnolly commentedLast patch revised with spaces instead of tabs:
Comment #7
dawehnerthe patch itself makes total sense for me
but i would check for !== because its faster
additional i realized a coding style problem in the function l()
here is a patch, which fixes the !== problem
i realized that your patch uses the old code style
"foo". $bar, corrected thisComment #8
damien tournoud commentedWhy do we call check_url() on the result of url()? Don't url() already protect us from harmful protocols by calling filter_xss_bad_protocol() itself when required? I understand that this patch has nothing to do with this, but this would require at least a comment if it's legit.
Comment #9
dawehneryes definitive
its also a (performance) bug in d6 and d5
the patch also fixes the coding style problem in #7
running tests at the moment
Comment #10
catchI noticed the multiple calls to filter_xss_bad_protocol() yesterday when cachegrinding HEAD, but hadn't looked to see where they were coming from yet. Nicely spotted - moved to #354812: filter_xss_bad_protocol is called hundreds of times on some pages. since it deserves it's own issue.
Comment #12
jody lynnComment #13
datarazor commentedHello, thanks for this patch. I'm using it on one site, this patch is indeed failing when run. As far as I can tell only:
Is required to allow "#" to be displayed. I'm not too sure why the other lines are in the patch since they are not changed?
Comment #14
dawehnerWow, that's pure nostalgia, a CVS patch :)
Not sure whether this issue is actually needed because you can achieve this using the following trick: http://api.drupal.org/comment/15669#comment-15669
Comment #15
dawehnerYeah, this is not needed anymore at that point in time.