Doesn't address bedwardly-down issue reported above
For that you need #2520
If you can post an example of code, how it's wrong and what you expect that might help. Making sense of big screenshots is hard.
For the record I've just tried some examples from your screenshot - red text, detail tag, and it's all working for me.
That's not an issue specific to that version, as far as I understand? We could add a bug report for this on GitHub though.
1 Like
You are right.
That's correct. It's most likely been around for awhile. I just discovered it on this release
The syntax <u>Some words</u> does not work in version 1.0.189. No underline.
@laurent, Here are my findings in detail.
The complete Markdown note
Who wins?
=========
##### H5
###### H6
<div class="different">
##### H5
###### H6
</div>
* * *
Should be <span style="color: red;">red</span>.
* * *
<style>
.different h5 { color: lightgreen; }
h5 { color: orange; }
h6 { color: orange; }
.different h6 { color: lightgreen; }
</style>
HTML generated by v1.0.179
<div id="rendered-md"><h1 id="who-wins">Who wins?</h1>
<h5 id="h5">H5</h5>
<h6 id="h6">H6</h6>
<div class="different">
<h5 id="h5-2">H5</h5>
<h6 id="h6-2">H6</h6>
</div>
<hr>
<p>Should be <span style="color: red;">red</span>.</p>
<hr>
<style>
.different h5 { color: lightgreen; }
h5 { color: orange; }
h6 { color: orange; }
.different h6 { color: lightgreen; }
</style>
</div>
HTML generated by v1.0.189
<div id="rendered-md"><h1 id="who-wins">Who wins?</h1>
<h5 id="h5">H5</h5>
<h6 id="h6">H6</h6>
<div class="different">
</div><h5 id="h5-2">H5</h5>
<h6 id="h6-2">H6</h6>
<<hr>
<p>Should be red.</p>
<hr>
<style>
.different h5 { color: lightgreen; }
h5 { color: orange; }
h6 { color: orange; }
.different h6 { color: lightgreen; }
</style>
</div>
Below is the rendering in the viewer, the generated HTML and the styling. Joplin 1.0.179 on Win10 is at the left side, and behaves as I expect (based on my knowlegde of CommonMark, HTML and CSS). The right side shows Joplin 1.0.189 on macOS Mojave. It has dropped some HTML, generated the </div> tag to early, choked on the explicit </div> tag, and skipped some styling directions.
My apologies for sending screenshots again. I could not find a way to retrieve the style specs from the development tool as text. And as you can see, there is a tiny discrepancy between the graphical representation of the HTML and its text format: the extra quoting of phrases. That’s why I include both formats in this post.
Thanks for providing the test cases. I’ve tested that yesterday evening and for sure red text for example was working in latest build. But I’ve been switching between wysiwyg branch and master several times so it’s possible I mixed something up. I’ll add this on GitHub to be checked before the final release.
- Joplin 1.0.189 (Portable)
- Windows 10 Pro x64
<mark>bla</mark>
is not rendered to Html, was working on 1.0.179
As an addition, ==bla== still works (when plugin ‘Enable ==mark== syntax’ is checked), but <mark>bla</mark> doesn’t (Joplin 1.0.189 on macOS Mojave).
This new version should normally take care of the recent HTML issues, and will also restore the template behaviour:
https://github.com/laurent22/joplin/releases/tag/v1.0.190
Please give it a try and let me know in particular if you still notice any HTML glitches.
Is note geolocation stamp working? I’ve checked it is enabled but am getting nothing in note properties.
Yep, I’ve just created a note and the geo location is available in the note properties.
On the Desktop app?
Yes. git master 8ba9e9ef
Thanks. Confirm works now on master (was broken in v187).
That’s weird, because the code for geo-location hasn’t changed between 187 and 190.
Yes, I noticed. I think it was a side-effect of something else (new note stuff).
https://github.com/laurent22/joplin/issues/2646# is getting worse…