We're developing a new site and using the built in WYSIWYG editor that ships with EPi. It renders diamonds in Firefox for element attributes, like
It isn't an encoding issue since we can use " anywhere else in the content. It's just when EPi renders these attributes that Firefox somehow put these diamonds around the value, which of course breaks its function.
Use the XHTML-string instead of the long string property.
It's in a custom property which inherits PropertyXhtmlString and PropertyLongStringControl
Hmm, never seen this with the xhtml-string property. Is there any difference between CurrentPage["PropertyName"], CurrentPage.Property["PropertyName"].Value, CurrentPage.Property["PropertyName"].ToWebString() and <episerver:property propertyname="PropertyName" runat="server" /> ?
The thing is, I'm storing multiple values in a XML document string using PropertyXhtmlString. If i set a breakpoint just before rendering the values, I'm seeing no garbage characters at all, they just magically appears in Firefox.