DevLobby 1.1.0

Five things that were quietly wrong, and a link that now goes somewhere.

What changed

A link that wants a new tab

target="_blank" did nothing at all, and the cause was a single attribute.
React discards a boolean given to an attribute it does not recognise, and
webview has no hyphen in it, so it was never a custom element to React —
allowpopups never reached the DOM, and Chromium refused every new tab in the
page before Electron could be asked about it.

It is now a question with three answers: a browser pane of its own beside
the page you were reading, nothing at all, or nothing from that pane for
five minutes — which is the one you want on a site that opens a tab every
time you touch it. No window is ever opened either way.

Hold Ctrl over a page

The same element picker, a modifier away. Hold Ctrl over a page and the
crosshair appears; click and the comment box opens on what you pointed at. It
is one comment and then it is over — no mode to enter, and none to leave. The
existing Select Element is still there for a sitting.

Comments are kept

They go into the state file with the layout, so they survive quitting DevLobby
and come back with the pane. A pane — or a whole grid — still holding comments
no session has collected asks before it closes, because a page you have marked
up is the one thing in a browser pane that reloading cannot get back.

The comments button turns everything off

One press of ⌖ puts the panel, the crosshair and a half-written comment box
away together. It used to close only the panel while leaving the page in pick
mode, which hid the very button that would have turned the selector off.

Clicking a tab stopped reordering the strip

A press was only cleared once it had become a drag, so an ordinary click left
one standing, and the next sweep of the pointer across the strip was read as
that press continuing. Grids are numbered by position when unnamed, so the
strip went on reading "grid 1, grid 2" while the two of them traded contents.

Also: a pane's URL is no longer wiped by its own guest reporting that it
arrived at about:blank before anything had pointed it anywhere, which could
cost a restored pane its page.

Download

devlobby-1.1.0-setup.exe	installs to your own user folder, so it never asks for admin, and adds Start Menu and desktop shortcuts
devlobby-1.1.0-portable.exe	one file, no install, no shortcuts

Windows x64. Your repositories, notes and layout live in %APPDATA%\DevLobby,
and upgrading over 1.0.0 leaves them alone.

If Windows blocks it

These builds are unsigned, so SmartScreen warns on first run — More info,
then Run anyway. Smart App Control, where it is enforced, judges each binary
by its hash and can refuse outright with "An Application Control policy has
blocked this file". Building from source and launching through devlobby.cmd
runs the same app through Electron's own signed binary, which that policy does
not object to:

npm install
npm run build
devlobby.cmd

The README has the screenshots
and the full tour.