Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

77%
+5 −0
Q&A QPixel goes to the "new post" page when I press Ctrl+N to open a new browser window

If I am on some web page (such as on Codidact), and want to check out some detail elsewhere on the web, my usual first step is to press Ctrl+N to open a new browser window, then navigate to do what...

0 answers  ·  posted 1y ago by Canina‭  ·  edited 1y ago by Monica Cellio‭

#4: Post edited by user avatar Monica Cellio‭ · 2023-12-04T04:22:58Z (about 1 year ago)
#3: Post edited by user avatar Canina‭ · 2023-06-13T17:53:30Z (over 1 year ago)
  • If I am on some web page (such as on Codidact), and want to check out some detail elsewhere on the web, my usual first step is to press Ctrl+N to open a new browser window, then navigate to do whatever it is I wanted to do.
  • Typically this works fine.
  • With QPixel it does not.
  • QPixel instead takes me to the "new post" in the original tab (alongside with my browser opening a new window), presumably because it catches the `n` and doesn't care about the fact that I was holding down Ctrl.
  • I consider this to be a bug. Even if keyboard shortcuts are turned on (which I really think that they shouldn't be by default, because they are extremely confusing to non-power-users), **QPixel shouldn't react to keyboard commands that just *happen to include* a QPixel keyboard shortcut key.**
  • (I also *had* turned keyboard shortcuts off, because I personally don't like web pages coopting input, so I guess I'll have to go through the communities and update that; but that's a different issue...)
  • If I am on some web page (such as on Codidact), and want to check out some detail elsewhere on the web, my usual first step is to press Ctrl+N to open a new browser window, then navigate to do whatever it is I wanted to do.
  • Typically this works fine.
  • With QPixel it does not.
  • QPixel instead takes me to the "new post" in the original tab (alongside with my browser opening a new window), presumably because it catches the `n` and doesn't care about the fact that I was holding down Ctrl.
  • I consider this to be a bug. Even if keyboard shortcuts are turned on (which I really think that they shouldn't be by default, because they are extremely confusing to non-power-users), **QPixel shouldn't react to keyboard commands that just *happen to include* a QPixel keyboard shortcut key.**
#2: Post edited by user avatar Canina‭ · 2023-06-13T17:40:42Z (over 1 year ago)
  • If I am on some web page (such as on Codidact), and want to check out some detail elsewhere on the web, my usual first step is to press Ctrl+N to open a new browser window, then navigate to do whatever it is I wanted to do.
  • Typically this works fine.
  • With QPixel it does not.
  • QPixel instead takes me to the "new post", presumably because it catches the `n` and doesn't care about the fact that I was holding down Ctrl.
  • I consider this to be a bug. Even if keyboard shortcuts are turned on (which I really think that they shouldn't be by default, because they are extremely confusing to non-power-users), QPixel shouldn't react to keyboard commands that just *happen to include* a QPixel keyboard shortcut key.
  • (I also *had* turned keyboard shortcuts off, because I personally don't like web pages coopting input, so I guess I'll have to go through the communities and update that; but that's a different issue...)
  • If I am on some web page (such as on Codidact), and want to check out some detail elsewhere on the web, my usual first step is to press Ctrl+N to open a new browser window, then navigate to do whatever it is I wanted to do.
  • Typically this works fine.
  • With QPixel it does not.
  • QPixel instead takes me to the "new post" in the original tab (alongside with my browser opening a new window), presumably because it catches the `n` and doesn't care about the fact that I was holding down Ctrl.
  • I consider this to be a bug. Even if keyboard shortcuts are turned on (which I really think that they shouldn't be by default, because they are extremely confusing to non-power-users), **QPixel shouldn't react to keyboard commands that just *happen to include* a QPixel keyboard shortcut key.**
  • (I also *had* turned keyboard shortcuts off, because I personally don't like web pages coopting input, so I guess I'll have to go through the communities and update that; but that's a different issue...)
#1: Initial revision by user avatar Canina‭ · 2023-06-13T17:39:50Z (over 1 year ago)
QPixel goes to the "new post" page when I press Ctrl+N to open a new browser window
If I am on some web page (such as on Codidact), and want to check out some detail elsewhere on the web, my usual first step is to press Ctrl+N to open a new browser window, then navigate to do whatever it is I wanted to do.

Typically this works fine.

With QPixel it does not.

QPixel instead takes me to the "new post", presumably because it catches the `n` and doesn't care about the fact that I was holding down Ctrl.

I consider this to be a bug. Even if keyboard shortcuts are turned on (which I really think that they shouldn't be by default, because they are extremely confusing to non-power-users), QPixel shouldn't react to keyboard commands that just *happen to include* a QPixel keyboard shortcut key.

(I also *had* turned keyboard shortcuts off, because I personally don't like web pages coopting input, so I guess I'll have to go through the communities and update that; but that's a different issue...)