Posts made by raphael-mioche

Hi,

bump, please.

Could you update the changelog?

Regards.

@raphael-mioche It’s still the same issue with v87.0.4390.58.

@ballzers I have the same issue too, in Opera GX LVL 3 v87.0.4390.56.

Could you fix this, please?

I think these other issues are related:
https://forums.opera.com/topic/55829/issue-incomplete-support-for-the-naming-of-keyboard-keys.
https://forums.opera.com/topic/55830/issue-keyboard-shortcuts-assigned-to-extension-features-don-t-support-non-qwerty-keyboards

Hi,

I have an AZERTY keyboard. I use French language on Windows 11 and Opera GX 86.

From the page: opera://settings/keyboardShortcuts If I assign a keyboard shortcut with “CTRL” + “Shift” + “B” keyboard keys to a default Opera feature the keyboard shortcut is defined as: Ctrl+Shift+B.

After that, I go to the bottom of this page, to customise the keyboard shortcuts for extensions features. If I assign a keyboard shortcut with “CTRL” + “Shift” + “B” keyboard keys to an extension feature the keyboard shortcut is defined as: Ctrl+Maj+B.

“Maj” in French means “Shift” in English.

Issue: So, we can configure two identical keyboard shortcuts for two different features (1 for default Opera feature Ctrl+Shift+B and 1 for extension feature Ctrl+Maj+B), and it results that when I use this shortcut Ctrl+Shift+B|Ctrl+Maj+B it’s the extension feature shortcut that works.

I think it shouldn’t be possible so set to identical keyboard shortcuts whatever the language keyboard used.

I think these other issues are related:
https://forums.opera.com/topic/55830/issue-keyboard-shortcuts-assigned-to-extension-features-don-t-support-non-qwerty-keyboards
https://forums.opera.com/topic/55831/issue-set-two-keyboard-shortcuts-maj-shift

I think these other issues are related:
https://forums.opera.com/topic/55829/issue-incomplete-support-for-the-naming-of-keyboard-keys
https://forums.opera.com/topic/55831/issue-set-two-keyboard-shortcuts-maj-shift

Hi,

I have an AZERTY keyboard. I use French language on Windows 11 and Opera GX 86.

From the page: opera://settings/keyboardShortcuts If I assign a keyboard shortcut with “CTRL” + “Shift” + “B” keyboard keys to a default Opera feature the keyboard shortcut is defined as: Ctrl+Shift+B.

Issue: To get a keyboard shortcut, dedicated to an extension feature, defined as: Ctrl+Maj+A I have to enter “CTRL” + “Shift” + “Q” keyboard keys.
For example:
If I enter the A keyboard key, I obtain a Q in the keyboard shortcut defined to a extension feature.
If I enter the Q keyboard key, I obtain an A in the keyboard shortcut defined to a extension feature.

Why the keyboard shortcuts dedicated to extension features (available at the bottom of this page) don’t support non-QWERTY keyboards?

Hi,

I have an AZERTY keyboard. I use French language on Windows 11 and Opera GX 86.

From the page: opera://settings/keyboardShortcuts If I assign a keyboard shortcut with “CTRL” + “Shift” + “B” keyboard keys to a default Opera feature the keyboard shortcut is defined as: Ctrl+Shift+B.

Issue: At the bottom of this page, we can customise the keyboard shortcuts for extensions features. So, if I assign a keyboard shortcut with “CTRL” + “Shift” + “B” keyboard keys to an extension feature the keyboard shortcut is defined as: Ctrl+Maj+B.

“Maj” in French means “Shift” in English.

Why Opera indicates “Shift” for keyboard shortcuts dedicated to default Opera features and “Maj” for keyboard shortcuts dedicated to extensions feature?

Hi,

I have an AZERTY keyboard. I use French language on Windows 11 and Opera GX 86.

From the page: opera://settings/keyboardShortcuts If I assign a keyboard shortcut with “CTRL” + “Shift” + “B” keyboard keys to a default Opera feature the keyboard shortcut is defined as: Ctrl+Shift+B.

1. First issue: At the bottom of this page, we can customise the keyboard shortcuts for extensions features. So, if I assign a keyboard shortcut with “CTRL” + “Shift” + “B” keyboard keys to an extension feature the keyboard shortcut is defined as: Ctrl+Maj+B.

“Maj” in French means “Shift” in English.

Why Opera indicates “Shift” for keyboard shortcuts dedicated to default Opera features and “Maj” for keyboard shortcuts dedicated to extensions feature?

2. Other issue: To get a keyboard shortcut, dedicated to an extension feature, defined as: Ctrl+Maj+A I have to enter “CTRL” + “Shift” + “Q” keyboard keys.

For example:
If I enter the A keyboard key, I obtain a Q in the keyboard shortcut defined to a extenion feature.
If I enter the Q keyboard key, I obtain an A in the keyboard shortcut defined to a extenion feature.

Why the keyboard shortcuts dedicated to extension features (available at the bottom of this page) don’t support non-QWERTY keyboards?

Hi Opera GX Team,

could you update the changelog in this topic, please?

Regards.

It seems the changelog re-appeared, thanks to the Opera GX Team!

Hi,

is there a chance to continue to read the changelog of each release from Opera GX on the topic below?

https://forums.opera.com/topic/33033/opera-gx-update-released

@kendle321 For some people, the difference between the colours by default of the links and the visited links is not sufficient.

@antena I have searched the same tool. I try many of these and now I use this: https://chrome.google.com/webstore/detail/color-links/hiponeioelghhaljfflaaflpccedbdem

Don’t forget to pin it this extension to use it where you want. For Google Search results, as leocg said, go to its Manage extension page to “Allow access to search page results”, and if you want to "Allow access on private pages".

@quik said in how to disable Tab Snoozing in the Opera GX?:

This happens when you have limiters enabled

I’m agree.

Only when memory limiter is activated, then the Tab Snoozing feature is activated.

@screwed38 said in [Request] Signal Private Messenger:

@raphael-mioche If thats the case then would it be possible to to have an extension that routes through the desktop app?

I think not, but ask them.

@s3nd41 As far I know it's not planed while it was already requested: https://www.reddit.com/r/signal/comments/brr65x/why_signal_has_no_web_based_interface/

@dinercim said:

Please add to Opera GX
In Opera Flags, activate:
chrome://flags/#player-service
chrome://flags/#player-service-control-panel

Then, the new Player button is displayed in sidebar but the 3 music player buttons are not displayed on the welcome Player page.

This is just a personal theory and I’m sorry for my english text.

I know that this kind of functionality exists: Imagine if the developers had access to our usage patterns. The areas (UI) of our web browser where we click on the most. Then it's easy for them to determine what functionality we use, how often, etc.

So, considering the total number of Opera users, on this subject we are frequent users of this feature and maybe we represent a minority regarding this usage. So, it is not hard to believe that these same developers have chosen to remove/hide this feature in favor of another one because we do not represent, we do not reach, their goal in terms of percentage of usage.

Do not forget that in a capitalist world, new functionalities are the most important thing, so keeping old features is not beneficial: for the Opera employee and for the potential new user of this software.