I don't understand the impact of having some non-escaped attributes. For example, the "url" view helper won't escape the "href" tag, however the "navigation" helper (More preciselly the "menu" plugin inside that view helper) will escape the "href" tag. The "itemtype" attribute of for schema.org is simply an absoulte url and it gets escaped... I may understand someone will wnt to escape the translated texts inside the "alt" atrribute, or something like that, but also not to escape some other attributes... Even the class names inside the "menu" plugin of the "navigtion" view helper get escaped. If the browser is homebrewed and hasn't taken care of it the output may get ruined. IMHO a framework should be so much involved on the output as it seems hard to sutomize this issue. If I'm not mistaken, in order to get non-escaped attributes I should write my own view helpers... As the MVC module will load the Zend\View View Helpers that means that in order to lower the resource I should also avoid using the Zend\Mvc namespace or, atleast change all the files under Zend\Mvc\Services to use my own so it will load my own application with my own services and, this way loading my custom ViewHelpers without loading Zend's. ¡That's a hell of task! But if I wish to maintain control over my output there seems to be no other solution. Atleast sticking to Zend Framework. I really don't understand the reason to enforce attribute escaping. I would understand it if it was a CMS or something of the kind, but beeing a Framework I guess it hould be up to the developer if he want to escape the attribute or not. In my case I wouldn't want to escape the attributes of the "htmlTag" which I'm using for the schema main itemtype. Neither i find it usefull to escape the attributes from the navigation menu. And there seems to be no easy way to solve this. Best regards
From: [email protected] Date: Mon, 18 Jan 2016 09:21:39 -0700 Subject: Re: [fw-general] Can we disable escapers for html attributes? To: [email protected] CC: [email protected] There is no problem (from an SEO perspective) in having escaped attributes. Also, UTF-8 is big and scary: don't disable escaping, it's just like asking for trouble ;-) Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 18 January 2016 at 07:51, Juan Pedro Gonzalez <[email protected]> wrote: Hi, I'm trying to add some schema.org for SEO but the attributes get escaped giving an ugly view of the code; further more, I'm not sure search engines will be able to handle this data the correct way. ¿Can't it be disabled?
