Published graph, page titles appear to be editable

[mklilley]

What happened?

When exporting public pages, the resulting webapp visually appears to be read only in most situations. This is as you would expect. For example, blocks are not longer editable when you click on their content. This is not the case for page titles - when you click on them you can edit them. This seems to be a bug from my perspective because there is no sense in which a user can edit a page title of a read-only graph.

There are a few other cases of apparent editable functionality in the read-only published graphs. For example, the delete button showing on the All Pages page and various options in the three dots menu. One can workaround these other examples by using custom CSS to hide the various components. The case of editable titles does not appear to be targetable via CSS - I have a sense that it's a JS thing.

Reproduce the Bug

1. Click on export graph in desktop app
2. Select export public pages
3. Select a folder to export the pages
4. Find the exported files and open the index.html file
5. Open a page from inside this read only published graph
6. Click on the title of that page - it appears editable

Alternatively, go to https://docs.logseq.com/ and start from step 5

Expected Behavior

Clicking on the title of a page in a read only published graph should do nothing. There should be no content editable functionality of the page contents or its title

Screenshots

No response

Desktop Platform Information

MacOS 12.0.1. Logseq Desktop 0.7.6

Mobile Platform Information

No response

Additional Context

No response

[candideu]

Try this for the CSS:

#main-container .page-title { 
   pointer-events: none; 
}

Kudos to @solarkraft's gist: https://gist.github.com/solarkraft/b05e9058ca2cda40a4d6e03c52dff025

[mklilley]

Thanks SO much @candideu !!!!

[solarkraft]

FWIW my gist attempts to resolve some more annoyances I've encountered (like images still having resize handles).

Sadly it can't deal with some of the more major bugs still present in the publishing feature like #4143. I wish it got some more attention since it's really cool (but it probably won't be from me since I've had a bit too hard of a time getting into Clojure).

[logseq-cldwalker]

Hi. This looks like a duplicate of #4552

[logseq-cldwalker]

Closing to keep track of the original issue in #4552. Can reopen if you'd like to change this issue to focus on other editing issues