Commit graph

13 commits

Author SHA1 Message Date
Renovate Bot 5beb1b56df Lock file maintenance 2024-10-21 02:05:21 +00:00
Renovate Bot 0c993085e0 Lock file maintenance 2024-09-30 02:03:35 +00:00
Renovate Bot 69b01eb911
Lock file maintenance 2024-09-25 10:15:02 +02:00
Renovate Bot e650b25bb6 Lock file maintenance 2024-08-19 02:05:17 +00:00
Renovate Bot 88169e74ed Lock file maintenance 2024-08-12 02:06:15 +00:00
Renovate Bot a3fa6c7d8e Lock file maintenance 2024-08-05 02:06:16 +00:00
Renovate Bot e7ed1d1ca2 Lock file maintenance 2024-07-29 00:04:22 +00:00
Renovate Bot fdf07888c3 Lock file maintenance 2024-07-22 00:07:27 +00:00
Renovate Bot 71f5dbccb6 Lock file maintenance 2024-07-15 00:07:24 +00:00
Renovate Bot e487dfbbc6 Lock file maintenance 2024-07-05 10:42:17 +00:00
Renovate Bot 15f9dde1c9 Lock file maintenance 2024-07-01 00:03:45 +00:00
silverwind 2cb07e8415
Regenerate fomantic lockfile and build it with our browserslist (#29560)
1. Make fomantic build use [our
browserslist](e3524c63d6/package.json (L99)).
I found no other way than to sed-replace into it's js, the normal
browserlist config files do not work. The effect of this change is the
removal of some uneeded CSS vendor prefixes.
2. Regenerate `web_src/fomantic/package-lock.json`, this might shut up
some security scanners.

---------

Co-authored-by: Giteabot <teabot@gitea.io>
(cherry picked from commit da3b7f5039158faae4b617ca878061f8a4f3e489)
2024-03-11 23:36:58 +07:00
wxiaoguang 4f3253feb9
Revert overflow: overlay (revert #21850) (#25231)
It causes not only one issue like #25221 (the footer width was also
affected by that change and was fixed some time ago)

The problem of "overflow: overlay" (#21850) is:

* It's not widely supported and is non-standard
https://caniuse.com/css-overflow-overlay
* It's not widely tested in Gitea (some standard layout like `ui
container + ui grid` may break it).
* The benefit seems smaller than the problems it brings.

So, I think it is good to revert it.

----

Let's leave enough time for testing and reviewing.

---------

Co-authored-by: Giteabot <teabot@gitea.io>
Co-authored-by: silverwind <me@silverwind.io>
2023-06-13 21:17:14 +02:00