Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time input on mobile only working in reading view and not in editing view #339

Closed
3 of 7 tasks
TtForge opened this issue May 22, 2024 · 3 comments
Closed
3 of 7 tasks
Labels
bug Undesired behavior caused by this plugin priority-high

Comments

@TtForge
Copy link

TtForge commented May 22, 2024

Please fill out these Check-boxes

  • I checked that the plugin is up to date
  • The issue persist with all other plugins and themes disabled

This Issue Occurs on

  • Windows
  • Linux
  • macOS
  • Android
  • iOS

Plugin Version

1.1.0

Describe the Issue

When using the time input field button, nothing happens when pressed unless I'm in reading mode. This started happening when I updated to a new version some weeks ago, when the buttons got redesigned, worked fine as a typed input before then. I can edit the time that is shown in the properties, but I can't open the android clock thing unless I'm in reading mode.

Steps to Reproduce

Simply just the time input field INPUT[time], nothing happens when pressed in editing mode, only opens the android clock screen in reading mode.

Expected Behavior

Works as intended in reading mode, so I would hope the exact same in editing mode.

@TtForge TtForge added the bug Undesired behavior caused by this plugin label May 22, 2024
@mProjectsCode
Copy link
Owner

Can reproduce, no idea why it is happening though. I need to take a closer look some other time.

@anareaty
Copy link

I have the same issue on Windows whith date, time and datetime inputs.

@mProjectsCode
Copy link
Owner

seems like my fix works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Undesired behavior caused by this plugin priority-high
Projects
None yet
Development

No branches or pull requests

3 participants