Closed (works as designed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
theme system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Oct 2014 at 19:27 UTC
Updated:
27 Oct 2014 at 21:25 UTC
Jump to comment: Most recent
Comments
Comment #1
star-szrThanks for creating this as a follow-up issue!
I could be missing something but I don't think #2324371: Fix common HTML escaped render #key values due to Twig autoescape changed anything with the syntax:
Also I think this is pretty standard IE conditional comment stuff, I'm not sure there's anything to be fixed in here but maybe you can provide more of an explanation.
Comment #2
star-szrhttp://www.quirksmode.org/css/condcom.html
I hate to say it but these do actually all start with
<!--and end with-->, so to me this works as designed.Comment #3
fabianx commentedTo clarify: #2324371: Fix common HTML escaped render #key values due to Twig autoescape did not introduce the comments, but rather marked them as safe:
is the relevant part of the diff.
Comment #4
mbrett5062 commentedComment removed to reduce noise as my original was incorrect.
Comment #5
mbrett5062 commentedThanks Cottser, I see now that most was correct, still a couple of things in question though. Ignore my last comment.
The only issue I still see is following.
$element['#prefix'] = SafeMarkup::set("\n<!--[if $expression]><!-->\n" . $prefix);Has another empty conditional comment at the end.
Should be:
$element['#prefix'] = SafeMarkup::set("\n<!--[if $expression]>\n" . $prefix);Plus
$element['#suffix'] = SafeMarkup::set($suffix . "<!--<![endif]-->\n");Has a double opening of the conditional comment.
Should be:
$element['#suffix'] = SafeMarkup::set($suffix . "<![endif]-->\n");Sorry for the noise and my confusion.
Comment #6
mbrett5062 commentedAnd having looked further I am able to close this issue. The special syntax on the last 2 is intentional, for browsers that are not IE.
Sorry for the noise, and thanks for your patience.
Comment #7
mbrett5062 commentedClosing this after further investigation. Thanks to @Cottser for pointing me in the right direction.
Comment #8
star-szrThanks for following it through @mbrett5062!