You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser & version: Safari Version 11.1.2 (13605.3.8)
Operating system: MacOs High Sierra 10.13.6
Was gonna file a "can't render :before pesudo element in safari" ticket, but then when I was trying to find a way to consistently recreate for you guys, I found that if the content value has a space anywhere, then the pseudo element would be recognized by the code and rendered on the image.
please note the footer in the images below:
this is the element on the footer I was changing.
.css-ubgfn1:before {
content: 'test with a space';
}
Please let me know if I can do a better job with documenting this bug.
I have also confirmed this with our own app with the version documented above (Just in case the version on the website is different).
For anyone who's might also use my "fix", we had to add in display:inline block to avoid the trailing/leading spaces to be rendered.
The text was updated successfully, but these errors were encountered:
Hi, so the pseudo :before element was added to the html in the footer of the website before the “created by” part of the footer. My screenshots are after html2canvas is done. You can see in the upper photo that the before element was added without a space and the rendered picture has no pseudo element.
However in the picture below the pseudo element has a space and it’s shown in the rendered image.
Note that this is a safari only bug.
The html2canvas rendered images are the modal-like image only. The attached images are my manual screen capture via Mac keyboard command.
Was gonna file a "can't render :before pesudo element in safari" ticket, but then when I was trying to find a way to consistently recreate for you guys, I found that if the content value has a space anywhere, then the pseudo element would be recognized by the code and rendered on the image.
please note the footer in the images below:
this is the element on the footer I was changing.
Please let me know if I can do a better job with documenting this bug.
I have also confirmed this with our own app with the version documented above (Just in case the version on the website is different).
For anyone who's might also use my "fix", we had to add in display:inline block to avoid the trailing/leading spaces to be rendered.
The text was updated successfully, but these errors were encountered: