6 Commits (5e9fd0ab5e3ce6428d6fe93c0c477fadb918e11f)

Author	SHA1	Message	Date
Giteabot	49f82ac4e3	Fix JS NPE when viewing specific range of PR commits (#27912) (#27923) ... Backport #27912 by @delvh This should be the easiest fix. While other solutions might be possible that exterminate the root cause, they will not be as trivial. Co-authored-by: delvh <dev.lh@web.de>	1 year ago
silverwind	ae8e8f055e	Use fetch helpers instead of fetch (#27026) ... WIP because: - [x] Some calls set a `content-type` but send no body, can likely remove the header - [x] Need to check whether `charset=utf-8` has any significance on the webauthn calls, I assume not as it is the default for json content. - [x] Maybe `no-restricted-globals` is better for eslint, but will require a lot of duplication in the yaml or moving eslint config to a `.js` extension. - [x] Maybe export `request` as `fetch`, shadowing the global.	1 year ago
silverwind	9a3de436f4	Reorder blocks in vue SFCs (#26874) ... The [recommended order](https://vuejs.org/guide/scaling-up/sfc.html) for SFC blocks is script -> template -> style, which we were violating because template and script were swapped. I do find script first also easier to read because the imports are on top, letting me immideatly see a component's dependencies. This is a pure cut-paste refactor with some removal of some empty lines. --------- Co-authored-by: Lauris BH <lauris@nix.lv>	2 years ago
wxiaoguang	4fdb09de58	Fix incorrect "tabindex" attributes (#26733) ... Fix #26731 Almost all "tabindex" in code are incorrect. 1. All "input/button" by default are focusable, so no need to use "tabindex=0" 2. All "div/span" by default are not focusable, so no need to use "tabindex=-1" 3. All "dropdown" are focusable by framework, so no need to use "tabindex" 4. Some tabindex values are incorrect (eg: `new_form.tmpl`), so remove them Co-authored-by: Giteabot <teabot@gitea.io>	2 years ago
silverwind	56b6b2b88e	Fix tooltip of commit select button (#26472) ... Previously, the tooltip for this button was only shown after opening and closing it once because it was only set after the server response, now it shows before opening it.	2 years ago
sebastian-sauer	55532061c8	Add commits dropdown in PR files view and allow commit by commit review (#25528) ... This PR adds a new dropdown to select a commit or a commit range (shift-click like github) of a Pull Request. After selection of a commit only the changes of this commit will be shown. When selecting a range of commits the diff of this range is shown. This allows to review a PR commit by commit or by viewing only commit ranges. The "Show changes since your last review" mechanism github uses is implemented, too. When reviewing a single commit or a commit range the "Viewed" functionality is disabled. ## Screenshots ### The commit dropdown  ### Selecting a commit range  ### Show changes of a single commit only  ### Show changes of a commit range  Fixes https://github.com/go-gitea/gitea/issues/20989 Fixes https://github.com/go-gitea/gitea/issues/19263 --------- Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: KN4CK3R <admin@oldschoolhack.me> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: delvh <dev.lh@web.de>	2 years ago