Opened 10 years ago
Closed 10 years ago
#28539 closed enhancement (duplicate)
Make more and nextpage tags beautiful (pure CSS) and translatable by converting them to wpviews
Reported by: | iseulde | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | TinyMCE | Keywords: | |
Focuses: | ui | Cc: |
Description
Patch includes patch for #28533 to make it work.
Now they also display well against all kinds of backgrounds, and no visible pixels when you zoom in.
Attachments (6)
Change History (13)
#3
@
10 years ago
I wish we had a __()
function in JS. :) We should probably split mce-view.js before localising it...
#4
follow-up:
↓ 5
@
10 years ago
- Keywords needs-patch added
- Milestone changed from Awaiting Review to Future Release
Not sure converting to wpViews is the best thing for these. Changing the placeholders from <img>
to <hr>
seems better. Then we can still use "more advanced" CSS, but keep things simple.
#5
in reply to:
↑ 4
@
10 years ago
Replying to azaozz:
Changing the placeholders from
<img>
to<hr>
seems better. Then we can still use "more advanced" CSS, but keep things simple.
I'm playing a bit with this and tried many things, including <hr>
and <table>
, but I always end up with something a bit hacky and not so future-proof.
Mr. Ozz, any objections to use TinyMCE noneditable plugin? Looks like it handles selection, caret position, dragging, delete, backspace and it would allow to use a normal inline element + CSS generated content instead of a void or replaced element where generated content is not guaranteed to work.
Added after and before screenshots with exactly the same content and theme.