#1502 closed defect (worksforme)
Cursor doesn't appear
Reported by: | Denis01 | Owned by: | Denis01 |
---|---|---|---|
Priority: | major | Milestone: | 2.1 |
Component: | html5 | Version: | trunk |
Keywords: | Cc: |
Description
Html client
Xpra version 2.1-r15507 64-bit
All the browsers
Usage with proxy.
On the start often cursor doesn't appear for text typing in text fields.
Sessions need to be rebooted
Change History (6)
comment:1 Changed 4 years ago by
Owner: | changed from Antoine Martin to Denis01 |
---|
comment:2 Changed 4 years ago by
1) I tried with 3 browsers: IE, Opera, Firefox - the same result.
2) Application - gedit
3) Today tried with proxy and directly - the same result.
4) Thanks for -d cursor. Tested with that right now. No errors.... everything is "blue" No special alerts.
5) Reboot the session - restart xpra session. With switch of keyboards: English layout in connection string and RU in tray, EN layout an En in tray etc. After several connect attempts (with different setting) system finally shows the cursor (have not figured out what is the logic....)
7) tried with r15512 and r15507 index.html settings - the same result.
8) if you would like you can see yourself 151_248_112_232 (port 10000 user and pass -111)
P.S. Could you please also see what can be done with #1461 ticket r15512 does not resolve the issue
comment:3 Changed 4 years ago by
Good news here.
Finally i came to the exact cause of error - the parameter (in html5 client) "Normal fullscreen window" impacts that.
I'll prepare more detailed description of error and will post it
comment:4 Changed 4 years ago by
Milestone: | → 2.1 |
---|
"Normal fullscreen windows" has already been removed in trunk, so it is likely I will just close this ticket as "invalid" or "wontfix": just don't use this deprecated feature.
comment:5 Changed 4 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Not heard back, closing.
comment:6 Changed 6 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1502
Please provide more details as per wiki/ReportingBugs.
Which exact browsers? Which applications are running via xpra? Browsers again? Which ones?
Is this only happening with the proxy? If so, do you have the proxy log output?
The is a "-d cursor" debug flag which may help.
I don't understand what "rebooting a session" would mean, or how that would fix things.