Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Posting this on d.o:
<ul>
<li>https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0#.q8xmja91n
<li>https://medium.com/@learnreact/container-components-c0e67432e005#.cb6jw5nxd
<li>http://jaketrent.com/post/smart-dumb-components-react/
</ul>
should linkify all three URLs. But the first is not. You'd think it's because of the @
, but you'd be wrong, because the second URL is linkified just fine.
Discovered at #2702061-67: Unify & simplify render & theme system: component-based rendering (enables pattern library, style guides, interface previews, client-side re-rendering). Attached screenshot of previewing a new node with just the above sample content proves that it's easily reproducible, and not a special edge case in that particular (complex) comment.
Comment | File | Size | Author |
---|---|---|---|
Screen Shot 2016-07-13 at 19.33.50.png | 29.71 KB | Wim Leers |
Comments
Comment #2
Wim LeersComment #3
Wim LeersI tried reproducing this in D8 core, but could not.
Comment #4
apadernoComment #5
TR CreditAttribution: TR commentedYes, this fails on any Drupal site running Drupal 7 using "Filtered HTML" or "Full HTML". Works on any Drupal site running Drupal 8. (But if you remove the underscore in @dan_abramov it works on a D7 site).
So it's not a webmaster issue for drupal.org, this is a problem with how the core filter module regexp parses links.
Moving to the core queue under the filter.module component.