Closed (duplicate)
Project:
Drupal core
Version:
8.0.x-dev
Component:
theme system
Priority:
Major
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
6 Jun 2015 at 16:12 UTC
Updated:
13 Jun 2015 at 18:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
peezy commentedWe're working on this as part of the NHDevDays code sprint.
Comment #2
dtraft commentedThis patch is the result of collaboration between @kbaringer, @peezy, @jbradley428, and @dtraft. Have at it, testbot!
Comment #4
dtraft commentedMinor consistency upgrades and Drupal coding standard compliance.
Comment #5
dtraft commentedFixing errors and small performance improvments
Comment #7
dtraft commentedSmall fix for casting type error.
Comment #10
peezy commentedUpdated Issue summary.
Comment #11
chrisfromredfinThat return was outside the loop, and I'm not sure why it was needed. At best, I can think that it was to avoid a SafeMarkup::format() call if there was nothing to call it in, so I used the ternary return based on non-empty $keys.
@kbaringer helped!
Comment #13
joelpittetUnfortunately
@!= toSafeMarkup::checkPlainit is =SafeMarkup::escape()which checks if it's safe before checkPlain'ing it. This means if you pass something fromt()through to atitleattribute for example and it has double quotes in it(like the failing tests), those quotes won't be escaped and the markup is broken.I'm going to add this to the postponed list till we figure out this joining issue:
#2501975: Determine how to update code that currently joins strings in SafeMarkup::set()
Comment #14
joelpittetComment #15
pwolanin commentedI'm not sure it makes sense to remove this call.
Comment #16
pwolanin commenteddup now to #2505701: Document SafeMarkup::set and Use htmlspecialchars() directly in Attribute() so we don't bloat the list of safe strings