Bug 125406 - Dialog theming/UX - some buttons keep the "pushed" state but should not
Summary: Dialog theming/UX - some buttons keep the "pushed" state but should not
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: iOS Editor (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other iOS
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-21 07:10 UTC by Nicolas Christener
Modified: 2024-04-15 03:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Video demonstrating the issue (569.73 KB, video/mp4)
2019-05-21 07:13 UTC, Nicolas Christener
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Christener 2019-05-21 07:10:50 UTC
Description:
Some buttons in tunneled dialogs in the iOS app keep the "pushed" state where they should probably not.

Steps to Reproduce:
1. Create/open a document in the iOS app
2. Select some text and open the hyperlink dialog
3. Enter an URL in the URL field and press "Apply"

Actual Results:
The button becomes blue and stays in the "pushed" state (at least that's my interpretation).

Expected Results:
The button should not stay blue and become "white" again.


Reproducible: Always


User Profile Reset: No



Additional Info:
I'll upload a video to demonstrate the issue.
Comment 1 Nicolas Christener 2019-05-21 07:13:33 UTC
Created attachment 151546 [details]
Video demonstrating the issue
Comment 2 Xisco Faulí 2019-05-27 11:35:03 UTC
Moving to NEW as agreed in the ESC meeting
Comment 3 Nicolas Christener 2020-04-14 18:01:14 UTC
The hyperlink dialog is not a tunneled dialog anymore, but there are other such cases, for example:

1. Create/open a writer document in the iOS app
2. Menu "Edit > Edit Style"
3. Tab "Tabs"
4. Button "Delete all"
Comment 4 QA Administrators 2022-04-15 04:00:48 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2024-04-15 03:15:23 UTC
Dear Nicolas Christener,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug