Continuing the discussion from Date selector in Topic Timer :
Problem
I tried to reproduce here, using multiple dates, and inserting code fences blocks, but it didn’t reproduce until
https://try.discourse.org/t/testing-insert-date-bug/1130/2 (this link will become obsolete by tomorrow, but it shows like the screenshot above.)
Cause
Finally I found the cause of the bug: the failing render follows an HTML tag with an attribute!
<abbr title="Coordinated Universal Time">UTC</abbr>
[date=2018-06-28 time=07:00 format=“HH:mm” timezones=“Europe/Brussels”]  [date=2018-06-28 time=15:00 format=“HH:mm” timezones=“Europe/Brussels”]
fails to render:
UTC
07:00 15:00
Solution
Avoid using HTML tags in Markdown – Or maybe implement <abbr> in CommonMark .
I suppose that an HTML tag appearing in a previous paragraph should not affect rendering later on though.
In any case: when things fail, check for a mix of HTML and Markdown.
Why do you need to use an emoji arrow? Use →
I simply pasted the result I got from using the ‘Insert Date’ button. The emoji transformation must be part of the cooking.
Edit: here is pasted the original character (or ➡ with backquotes)
Edit:
'➡'.unpack('U*')
=> [10145]
j.jaffeux
(Joffrey Jaffeux)
28 يونيو 2018، 10:14م
4
Yes ➡ will be cooked as an emoji
I will give it a look to this tomorrow.
Test:
A
07:00
إعجابَين (2)
j.jaffeux
(Joffrey Jaffeux)
4 يوليو 2018، 9:50م
5
لا علاقة لهذا الأمر بإدراج التاريخ. إنه قيد مفروض على textPostProcess
على سبيل المثال، سيفشل الأمر أيضًا مع التصنيفات؛ ستعمل الأولى، لكن أي شيء يأتي بعد abbr لن يعمل (كما ذكر @sam ):
Contribute > Feature
<abbr>A</abbr>
A
Contribute > Feature
فهمي هو أن الكتلة التالية بعد abbr ستُحوَّل إلى فقرة ولن تُفسَّر بواسطة textPostProcess. هذا سلوك ناتج عن مُنقّينا https://github.com/discourse/discourse/blob/master/test/javascripts/lib/sanitizer-test.js.es6#L117:
@sam ، هل لديك أي فكرة حول هذا الأمر من فضلك؟ هل تظن أنه يستحق الإصلاح؟ يبدو لي أنه حالة هامشية للغاية للغاية.
sam
(Sam Saffron)
4 يوليو 2018، 10:16م
6
Something is not right internally cause <small> does not cause this issue nor does <sub> or <ins> or <kbd>
I am guessing this is something internally is broken in sanitizer that is specific to this inline tag. Probably worth fixing.
sam
(Sam Saffron)
4 يوليو 2018، 11:28م
7
4 إعجابات
sam
(Sam Saffron)
تم إغلاقه في
6 يوليو 2018، 8:00ص
8
This topic was automatically closed after 32 hours. New replies are no longer allowed.