Add Op specific actions to contextMenu
Show context menu when left clicking user
Switch to using data attributes as selectors
remove ban as possible action
Move `isOpInChannel()` to utils.js
Capitalize strings
use CSS.escape for `ownNick`
use string interpolation
properly point to findCurrentNetworkChan
Move context menu item actions to command pattern
add icons for context menu actions
Make list in context menu always list.
remove empty lines in style.css
use info circle instead of question circle
change context menu labels.
change contextMenuActions.execute to more explicit method.
- Separate messages by one more pixel: the recent font changes make multiline messages rather hard to differentite from one another. I believe adding 2px looked better, but I knew that would cause riots so I went for a middle ground 😅
- Make previews the same size than messages themselves, and adapt the thumbnail height accordingly
- Make the message input font size same as message size
It is currently impossible to edit the nick text after pressing the edit button on Safari for iOS and Mac because user-select is set to None on Safari by default. This fixes that issue. Tested that it is not editable when it shouldn't be and that it doesn't break anything on Chrome or Firefox.
This could be reproduced on tablet or large phone (as long as portrait mode shows a collapsible menu and landscape mode shows normal menu) or when resizing the browser on desktop.
- Close button and badge are now positioned using the same method. Previously one was float and the other was absolutely positioned.
- Increase the close button size to match 2.4.0, as it was made smaller when moving to the native font stack.
- Removed link margins on left/right of the channel links, and the `1px` gap between links.
- Removed hack/fix for drag-and-drop now made unnecessary
This option is less and less the norm on modern webapps, it is fair to assume this is the default behavior. In fact, we were making it the default.
But more importantly, coming soon is the ability of remotely logging out of your other sessions, which is well handled through token deletion. That means we need to know about said tokens, which are not sent in no-"Stay signed in" version.
