Svg element removed from x-text in safari

Support
#1

I have an svg element that I have placed into an t-text cornerstone element that is removed in safari. place the same svg element into an raw-content cornerstone element and the svg appears as it should in safari.

furthermore i have the svg wrapped in a button. I gave the button various attributes however none of the attributes except for the class appear in safari.

it sounds like some html character encoding difference between the two cornerstone elements, resulting in issues with safari. for example.

to see an example of this you can go to hallerpainting.net

#cs-content .x-section#jeremy .x-text.notContinue button //svg does not appear here and button attributes are missing
//the button above is set to display none since this site is live. as you will notice if you look at it with any other browser but safari I’m hiding it with both and inline style and page css, since the inline style is removed in safari.
#cs-content .x-section#jeremy .x-text.notContinue + .x-raw-content button //everything works fine here

#2

Hi there,

The Text element is not a suitable place to add SVG code. Text element strips out some tags and functionalities due to its nature of being text element and other options that are added to the element.

You will need to keep using the Classic Raw Element to add your SVG code.

Thank you.

#3

I don’t think you fully understood what I was trying to say. I’ve moved over to using the raw content so I don’t have any immediate problem, however I’m trying to alert you to an issue. The text element seems to be susceptible to outputting improperly formatted html, which is causing disparities between browsers. Safari as mentioned removed a lot of stuff from my text element.

#4

Hi there,

Sorry for confusion.

Can you please post your website login details and pointing to the page section that you are facing issue in a secure note so that we can have a look.

Thanks

#5

Hi there,

I totally understand what you mean, but the point is that the Text element is not intended to have the wide variety of HTML code. Most of the iFrame, Embed, Object, SVG and this kind of tags might be stripped out and cause the problem in Safari. This is because in most cases we escape the HTML code to ensure the integrity of the element and the other options attached to it will hold.

That is why it is not recommended to have such stuff in a text element. Raw Content in contrary does not have additional options which might break and it can be used for that kind of tags.

The Text Element behavior will not change as it needs to escape stuff to make sure the other options attached to it will always work properly.

I hope I could explain the case. Thank you.

#6

Unfortunately despite your assertion I don’t think you understand.

  1. I have found a solution to the problem and don’t need “support”.

  2. I’m alerting you to an issue with your product.

I’m a developer.

If I develop something that doesn’t function the same cross-browser I believe that is a problem. It is a problem because visitors expect things to just work, regardless of what browser they are in, if they are even aware that there are different browsers. Visitors shouldn’t have to worry about what browser they are viewing a website with.

It is also a problem because unless I intended something to behave differently in one browser, then its not behaving as I had anticipated which suggests that if I didn’t foresee this deficiency then there might be other ancillary and as of yet unknown issues.

So if the neither idea of users experiencing your site differently based on the browser they view it with, or the idea that there might be unknown unintended behaviors associated with a known issue, bother you then I don’t think we have anything further to discuss.

#7

Hello There,

Sorry for the confusions. We have noted your feedback and add in our issue tracker so that our developers will be made aware of it.

Thank you for your understanding.

#8

Thanks. Sounds good.

#9

You’re welcome, have a great day.

Cheers!

#10

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.