Skip to content

fix: numrow for shifted numbers#54

Draft
mancellin wants to merge 1 commit into
OneDeadKey:mainfrom
mancellin:fix_shifted_numrow
Draft

fix: numrow for shifted numbers#54
mancellin wants to merge 1 commit into
OneDeadKey:mainfrom
mancellin:fix_shifted_numrow

Conversation

@mancellin

@mancellin mancellin commented May 12, 2026

Copy link
Copy Markdown

Edit: opened the PR too early. I'm still testing this.

@mancellin mancellin marked this pull request as draft May 12, 2026 20:00
@Nuclear-Squid

Copy link
Copy Markdown
Collaborator

Thanks for your contribution !

I’ll have to discuss it with other maintainers, but since this technically breaks the specification (who describes having Shift + Numbers on the top row), we’ll probably need to update it before we merge this.

I’ll try to chat with other Selenium users with Azerty or Bépo, but I think I like having numbers in a consistent location. Just need to make sure they share this sentiment

CC @Ashenfae

@Ashenfae

Copy link
Copy Markdown
Collaborator

I find it makes sense to have the numbers in a specific location, as you said, especially with the number‐related symbols on the RH bottom row. So, on the principle, I’d be in favor, but I agree that it would be better to have the opinion of someone using Azerty and/or Bepo (and that the spec will need to be updated first if we confirm we want to go through with it, but that’s a trivial change in formulation).

@mancellin

Copy link
Copy Markdown
Author

Sorry for the under-cooked PR, and thanks for your feedback already.

To give some more background, I'm using Azerty and I'm a bit frustrated by the numrow layer. Some digits are not very comfortable to access and all the characters on the home-row are already accessible in more logical positions somewhere else.

By the way, the Kanata implementation of Arsenik has the number on the home-row of the numrow layer, even in Azerty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants