Skip to content

js: Revert change to click behaviour in forceSelection #8921

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

Merged
merged 2 commits into from
Nov 11, 2019
Merged

js: Revert change to click behaviour in forceSelection #8921

merged 2 commits into from
Nov 11, 2019

Conversation

Jookia
Copy link
Contributor

@Jookia Jookia commented Nov 11, 2019

Calling .click() in forceSelection() in blur() causes a focus loop,
this needs a proper fix later but for now just revert the change.

(Hotfix for #8919)

Calling .click() in forceSelection() in blur() causes a focus loop,
this needs a proper fix later but for now just revert the change.
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Nov 11, 2019
@codecov-io
Copy link

codecov-io commented Nov 11, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@561044e). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #8921   +/-   ##
=========================================
  Coverage          ?   41.21%           
=========================================
  Files             ?      546           
  Lines             ?    70573           
  Branches          ?        0           
=========================================
  Hits              ?    29087           
  Misses            ?    37788           
  Partials          ?     3698

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 561044e...df786fa. Read the comment docs.

@zeripath zeripath added the issue/regression Indicates a previously functioning feature or behavior that has broken or regressed after a change label Nov 11, 2019
@zeripath zeripath added this to the 1.11.0 milestone Nov 11, 2019
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Nov 11, 2019
@zeripath zeripath merged commit 173da1b into go-gitea:master Nov 11, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/regression Indicates a previously functioning feature or behavior that has broken or regressed after a change lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants