-
Notifications
You must be signed in to change notification settings - Fork 800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Video sitemap description: change the XSL Stylesheet to display the HTML #13261
Conversation
Caution: This PR has changes that must be merged to WordPress.com |
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: September 3, 2019. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to work well in my tests. 👍
What happens when there's "weird" HTML in the description. Images, for example? Does the output look ugly to humans? Should we run the description through kses? |
Yeah, interesting case, which I have not thought of yet! I've tried all possible tags when editing a media file.
We can do that but we may lose the visibility of other HTML tags to search engines. I would vote not doing this :D My detailed testDescription HTML code
This is the result in 100% browser size:This is the result in 75% browser size: |
htdat, Your synced wpcom patch D31677-code has been updated. |
I tweaked the stylesheet in 8fa1d91 to limit the size of images. I'm fine merging this. Let's be clear with the user reporting the issue, though, that the HTML tags (including the wrapping Firefox, for example, ignores the |
* 7.7 changelog: initial set of changes * Changelog: add #13154 * Changelog: add #13134 * Changelog: add #12699 and many others * Changelog: add #13127 * Changelog: add #13167 * Changelog: add #13225 * Changelog: add #13179 * Changelog: add #13173 * Changelog: add #13232 * Changelog: add #13137 * Changelog: add #13172 * Changelog: add #13182 * Changelog: add #13200 * Changelog: add #13244 * Changelog: add #13267 * Changelog: add #13204 * changelog: add #13205 * Changelog: add #13183 * Changelog: add #13278 * Changelog: add #13162 * Changelog: add #13268 * Changelog: add #13286 * Changelog: add #13273 * Changelog: add #12474 * Changelog: add #13085 * Changelog: add #13266 * Changelog: add #13306 * Changelog: add #13311 * Changelog: add #13302 * Changelog: add #13196 * Changelog: add #12733 * Changelog: add #13261 * Changelog: add #13322 * Changelog: add #13333 * Changelog: add #13335
r206613-wpcom |
Fixes #9546
Changes proposed in this Pull Request:
disable-output-escaping='yes'
, humans can see rich texts with HTML rather than HTML-escaped tags.Is this a new feature or does it add/remove features to an existing part of Jetpack?
Testing instructions:
<strong>Description</strong> with <a href="https://github.com/Automattic/jetpack/issues/9546">HTML tags</a>.
Proposed changelog entry for your changes: