-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
iOS safari returns to the previous page after entering the repository and there will be a js error #24784
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
Comments
Likely the same in #24770 |
24770 could be another problem IMO. That issue about "user randomly gets logged out". I guess this issue is related to other problems if it keeps reproducing. |
@wxiaoguang That would be bad. Why the good couple(gitea and safari) suddenly fall apart :) |
Apple also used to make new bugs (it could also be a bug on Gitea side) If you google "safari blahblah", there are more bugs than Chrome. |
I can attest, Safari is currently the most buggiest browser engine around, by a big margin. |
You can check that the error message is not displayed when the Safari browser is used |
…#25089) - Enable all source maps in dev build - Disable all source maps in prod build - Provide `ENABLE_SOURCEMAP` env var to override it. I think the strange error seen in #24784 is sourcemap related, so if we enable/disable them all, it might go away. But it's most definitely a Safari bug. With all sourcemaps disabled, binary size goes down by around 1-2 MB, with all enabled it goes up by around 12MB. If +12MB is acceptable, we could also always enable them by default as fully source maps do have some debugging benefits.
Can we close this issue if it is done. |
I don't think it's solved unfortunately. |
Description
No response
Gitea Version
1.20.0+dev-833-g040970c32
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
at try.gitea.io
Database
None
The text was updated successfully, but these errors were encountered: