Jump to content

Topic on Project:Support desk

Remove Same-Page Preview?

8
Summary by Johnywhy

MediaWiki:Common.css

#wikiPreview{
    Display:none;
}
Johnywhy (talkcontribs)

when i enable side-by-side preview, i still get same-page preview (below edit area).

i don't need both.

how to remove same-page preview?

thx

AhmadF.Cheema (talkcontribs)

MwdiaWiki:Common.css:

#wpPreviewWidget {
   display:none;
}

But remember that the "side-by-side preview" preview is deprecated and will probably soon be removed from newer versions of WikiEditor and if at that time you have this rule enabled, your users will have no preview options available.

Johnywhy (talkcontribs)

Thx for css!

Very unfortunate to hear about loss of side-by-side.

It's visual language is easier to understand, because you can compare sub-sections with a quick toggle. Key-stroke would be nice.

2-pane might also be a good idea. The more quickly and conveniently you can compare line-by-line, word-by-word, the more useful is the preview.

For me, the vertical below or above arrangement is the least convenient of all. If you're writing a long page, it's awkward to scroll to it. You can't quickly compare sub-sections.

I hope future versions will be easy to customize.

I wonder how hard it would be to rip out the existing side-by-side code, and serve it up as an extension?

Wysiwyg is of course best. TinyMCE has bugs.

cheers!

AhmadF.Cheema (talkcontribs)

The Preview tab is definitely, for me, the most used feature of the WikiEditor. I almost never use any of the edit buttons or CharInsert, but the preview has always been a must. The full page preview forces a refresh of the page, renders too much content on the page, and the user looses their place on the web-page.

Unfortunately, for whatever reason, the developers have apparently now completely focused on VisulaEditor and its related 2017 wikitext editor, which for a lot of small-scale personal Wiki administrators is too resource intensive to implement.

Johnywhy (talkcontribs)

Exactly, everything you said.

I can't even use VisualEditor, because my webhost does not support node.js

What is the process to communicate ourselves to developers?

Re common.css, i dont have `wpPreviewWidget`. Following works on my MW v1.30.

#wikiPreview{
    Display:none;
}
AhmadF.Cheema (talkcontribs)

Are you sure it isn't a cache issue, with changes showing up late?

I don't think #wikiPreview does anything in this context.

Johnywhy (talkcontribs)

i waited some time for CSS to take effect. I'm assuming if i change common.css, and then see a change on the frontend after 10 minutes, it's the most recent change i'm seeing, and not some older edit.

Also, when i test with browser css injector, #wikiPreview works, but #wpPreviewWidget doesn't.

I can see wikiPreview in page source:

https://image.ibb.co/h6nf5S/Screenshot_283.png

AhmadF.Cheema (talkcontribs)

Oh, OK. I thought you wanted to hide the "Show Preview" button that creates the full page preview. Didn't know you wanted to hide the created preview.

For new CSS to take effect, you have to do a hard refresh (Ctrl + R) of the browser.