5 Commits (3e7101dd64e4cd5d9ecfd4dbe0c991aacf99bf87)

Author	SHA1	Message	Date
wxiaoguang	1c8bc4081a	Show friendly 500 error page to users and developers (#24110) ... Close #24104 This also introduces many tests to cover many complex error handling functions. ### Before The details are never shown in production. <details>  </details> ### After The details could be shown to site admin users. It is safe. 	2 years ago
Xinyu Zhou	dd7f1c0334	Quick fixes monaco-editor error: "vs.editor.nullLanguage" (#21734) ... fixes: https://github.com/go-gitea/gitea/issues/21733 Uncaught Error: Language id "vs.editor.nullLanguage" is not configured nor known Note that this monaco-editor worked fine on 0.33.0 and broke on 0.34.0. If upstream fixed, remove this code. Signed-off-by: Xinyu Zhou <i@sourcehut.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	2 years ago
silverwind	32159cc4a3	Fix mermaid-related bugs (#21431)	2 years ago
wxiaoguang	f5c97172f0	Bypass Firefox (iOS) bug (#20244) ... * https://github.com/go-gitea/gitea/issues/20240 At the moment, Firefox (iOS) (10x) has an engine bug. See https://github.com/go-gitea/gitea/issues/20240 If a script inserts a newly created (and content changed) element into DOM, there will be a nonsense error event reporting: Script error: line 0, col 0. This PR ignores such nonsense error event. Fix #20240	2 years ago
wxiaoguang	2bce1ea986	Show messages for users if the ROOT_URL is wrong, show JavaScript errors (#18971) ... * ROOT_URL issues: some users did wrong to there app.ini config, then: * The assets can not be loaded (AppSubUrl != "" and users try to access http://host:3000/) *The ROOT_URL is wrong, then many URLs in Gitea are broken. Now Gitea show enough information to users. * JavaScript error issues, there are many users affected by JavaScript errors, some are caused by frontend bugs, some are caused by broken customized templates. If these JS errors can be found at first time, then maintainers do not need to ask about how bug occurs again and again. * Some people like to modify the `head.tmpl`, so we separate the script part to `head_script.tmpl`, then it's much safer. * use specialized CSS class "js-global-error", end users still have a chance to hide error messages by customized CSS styles.	3 years ago