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.

Sign up for GitHub

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

Jump to bottom

WireUI don't work with Chrome < v.80 on Android #51

Closed
trippo opened this issue Jul 27, 2021 · 14 comments
Closed

WireUI don't work with Chrome < v.80 on Android #51

trippo opened this issue Jul 27, 2021 · 14 comments
Labels
browser support Unsupported browser feature
Projects
TODO Components

Comments

@trippo
Copy link
Contributor

trippo commented Jul 27, 2021

Wireui don't work with chrome browser on android.

If you try to load the page you have an error:
VM28:71 Uncaught SyntaxError: Unexpected token '.'
also on documentation page
https://livewire-wireui.com/docs/get-started
@PH7-Jack
Copy link
Member

What's the android version?
What's the chrome version?

@trippo
Copy link
Contributor Author

trippo commented Jul 27, 2021

Mi test phone has
Android 6
Chrome 79

@trippo
Copy link
Contributor Author

trippo commented Jul 27, 2021 •
edited

The problem is Optional chaining '?.' on alpine js code on blade components

@trippo
Copy link
Contributor Author

trippo commented Jul 27, 2021

Example on notification message
image

@trippo
Copy link
Contributor Author

trippo commented Jul 27, 2021

I found the problem
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining
image

@trippo trippo changed the title WireUI don't work with chrome on Android WireUI don't work with Chrome < v.80 on Android Jul 27, 2021
@trippo
Copy link
Contributor Author

trippo commented Jul 27, 2021

What do you think about?

@PH7-Jack
Copy link
Member

PH7-Jack commented Jul 27, 2021 •
edited

I'm taking a look, as I see you are correct. Previous versions are not supported, even other browsers from what I've found out. I'm thinking of a way to solve this in all unsupported browsers.
Maybe a function like "data_get()" from laravel, but for js

@PH7-Jack
Copy link
Member

https://caniuse.com/mdn-javascript_operators_optional_chaining

@PH7-Jack PH7-Jack added browser support Unsupported browser feature bug Something isn't working and removed bug Something isn't working labels Jul 27, 2021
@trippo
Copy link
Contributor Author

trippo commented Jul 27, 2021

I think it's a great solution

@PH7-Jack PH7-Jack added this to To do in TODO Components Aug 5, 2021
@PH7-Jack PH7-Jack moved this from To do to In progress in TODO Components Aug 5, 2021
@PH7-Jack
Copy link
Member

Update: Added support for chrome 71+. I'm testing with firefox, safari, and the like
I'm refactoring many things, soon I have great news

@PH7-Jack
Copy link
Member

Are working in

  • safari 12.1+
  • safari ios 12.2+
  • chrome 71+
  • chrome android 71+
  • firefox 69+
  • firefox android 79+

@PH7-Jack
Copy link
Member

In soon I will release a new version with this fix

@PH7-Jack
Copy link
Member

Websites to simulate browser

@PH7-Jack
Copy link
Member

PH7-Jack commented Sep 29, 2021 •
edited

The new version is now released. Can you try using the latest version?
If the problem persists, reopen the issue

@PH7-Jack PH7-Jack moved this from In progress to Done in TODO Components Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
browser support Unsupported browser feature
Projects
No open projects
TODO Components
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@trippo @PH7-Jack