I wonder if shouldAllowPublic() was just forgotten or if the idea behind was to exclude web crawlers (as querying those lists en-masse could be expensive).

Most of these can be done by adding the following to controller files related to query, list, and view files:

Knowing rHP will be replaced by R10, I will submit a patch to close this task.

This is forgotten, and honestly not something really required.

I've set can create to Trusted Contributors for now. I don't see a problem with people being able to create documents.

Currently limited to Trusted Contributors, which is enough as these users can be trusted not to break this install.

It returned to function again. Not sure why it wasn't working but good to see it working again.

In T15979#20270, @avivey wrote:

@Cigaryno which browser/OS are you using?

(I cannot reproduce anymore, now I see the very - ugly - native desktop notification of my environment lol; but it's difficult to note since I've configured my computer to disappear after 0.5 seconds - also maybe a common problem I guess)

The "Grant permission" button works for me on Chrome/Windows.

You are totally right, I've never seen native browser notifications too. For some reasons I've always confused Phorge's popup with these since they are quite similar in my environment

In T15979#20265, @valerio.bozzolan wrote:

Is there a possibility that you have a browser extension privacy-focused that automatically denies this permission?

Is there a possibility that you have a browser extension privacy-focused that automatically denies this permission?

Any error in your browser console?

Clicking on Send Test Notification, a notification shows up on the bottom of the screen, but this is totally unrelated to browser notifications.
After clicking on the Grant Permission button:

Can you share a screenshot after you click on that button?

I proposed two related patches in D25683 and D25685, both of them obsoleted by: D25687.

In T15056#3210, @golyalpha wrote:

Another example of broken dark theme