Skip to content

Fix #1271: Call location.reload after XHR finishes - #2071

Merged
lunny merged 1 commit into
go-gitea:masterfrom
knixeur:fix1271
Jun 28, 2017
Merged

Fix #1271: Call location.reload after XHR finishes#2071
lunny merged 1 commit into
go-gitea:masterfrom
knixeur:fix1271

Conversation

@knixeur

@knixeur knixeur commented Jun 28, 2017

Copy link
Copy Markdown
Contributor

location.reload was being called when the related dropdown
was hidden, even if a request initiated before to update this
value hadn't finished. This caused troubles on Firefox.

Please check the following:

  1. Make sure you are targeting the master branch, pull requests on release branches are only allowed for bug fixes.
  2. Read contributing guidelines: https://github.com/go-gitea/gitea/blob/master/CONTRIBUTING.md
  3. Describe what your pull request does and which issue you're targeting (if any)

You MUST delete the content above including this line before posting, otherwise your pull request will be invalid.

location.reload was being called when the related dropdown
was hidden, even if a request initiated before to update this
value hadn't finished. This caused troubles on Firefox.
@lunny lunny added this to the 1.2.0 milestone Jun 28, 2017
@lunny lunny added the type/bug label Jun 28, 2017
@lunny

lunny commented Jun 28, 2017

Copy link
Copy Markdown
Member

Great. LGTM will fix #1271. Thanks!

@tboerger tboerger added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jun 28, 2017
@lafriks

lafriks commented Jun 28, 2017

Copy link
Copy Markdown
Member

This should probably be reworked in 1.3 not to reload page at all but otherwise LGTM

@tboerger tboerger 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 Jun 28, 2017
@lunny
lunny merged commit 858197b into go-gitea:master Jun 28, 2017
@lunny

lunny commented Jun 28, 2017

Copy link
Copy Markdown
Member

@lafriks let's merge this at first.

@lafriks

lafriks commented Jun 28, 2017

Copy link
Copy Markdown
Member

@lunny yes, of course, that should be other PR after 1.2.0 is released

@knixeur
knixeur deleted the fix1271 branch June 28, 2017 13:03
@lunny

lunny commented Aug 11, 2017

Copy link
Copy Markdown
Member

It seems this PR is difficult to back ported to v1.1. I have gave up this.

@bkcsoft

bkcsoft commented Aug 23, 2017

Copy link
Copy Markdown
Contributor

@lunny Have you checked that this needs doing on v1.1.3?

@lunny

lunny commented Aug 23, 2017

Copy link
Copy Markdown
Member

Yes, v1.1.4

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants