bidmead

Thanks, James, for following through with this. I don’t want to prolong the thread but let me try to make amends for not making myself clear.

If links are to be permitted in some discussions but not in others (a reasonable condition) and if bbPress is to be used for all discussions, wouldn’t it be sensible to design bbPress with what I’m calling a “context sensitive switch”?

Allowing it to be evoked in some discussions as bbPress --no-links.

The size of the FJ dialogue box, of course, varies with the zoom factor of the browser. I could probably juggle with the font size and zoom to make the box smaller (yes, a “compact” version, about half the current dimensions) but that might mess with other aspects of my editing.

This really is no big deal. Neither is the positioning issue. (My inclination would be to move it down until it’s just a few pixels above the bottom of the screen. Ideally, this placement would be something the user could do with the mouse cursor, with the position remaining sticky between sessions.)

One other—again very minor—point: the Sliding Effect is described as only applying to “screens/resolutions >=1200px wide”. This led me to suspect that it was dependent on the 2256×1504 screen resolution I’m using for Ubuntu on this Framework laptop. In fact, it appears to depend on the current zoom factor of my Vivaldi browser. Set to the 125% I use as standard, the Sliding Effect is non-functional. At 100% zoom it works nicely. It would be good to be able to slide at whatever zoom factor I choose.

—
Chris

I understand why links are allowed in some cases but not in others. Just baffled that this protocol isn’t implemented, therefore, in the bbPress code as a context-sensitive switch.

Or, if there is a switch—my original assumption—what’s the reason for not using it?

The design principle being breached here is that users shouldn’t be offered the option to do what they’re not allowed to do. My surprise was at finding that WordPress seems not to have learnt this over the course of its two decades as a world-leading CMS.

—
Chris