The source project of this merge request has been removed.
After highlighting, update url of file action buttons.
What does this MR do?
I have fixed operating logic of file action buttons.
Are there points in the code the reviewer needs to double check?
I don't think so.
Why was this MR needed?
After highlighting, when I push permalink or blame button, my highlights disappear. It was kind of unnerving.
What are the relevant issue numbers?
Fixes #19742 (closed)
Screenshots (if relevant)
I will upload a video which is about how it works.
Does this MR meet the acceptance criteria?
-
CHANGELOG entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the style guides -
Branch has no merge conflicts with master
(if you do - rebase it please) -
Squashed related commits together
Merge request reports
Activity
Added 1 commit:
- 029b04ac - CHANGELOG was updated.
Marked the task CHANGELOG entry added as completed
146 148 # We're using pushState instead of assigning location.hash directly to 147 149 # prevent the page from scrolling on the hashchange event 148 150 history.pushState({turbolinks: false, url: value}, document.title, value) 151 152 @__updateFileActionButtons__(value) 153 154 # After highlighting, update url of file action buttons. 155 __updateFileActionButtons__: (hash) -> 146 148 # We're using pushState instead of assigning location.hash directly to 147 149 # prevent the page from scrolling on the hashchange event 148 150 history.pushState({turbolinks: false, url: value}, document.title, value) 151 152 @__updateFileActionButtons__(value) 153 154 # After highlighting, update url of file action buttons. 155 __updateFileActionButtons__: (hash) -> 156 $buttons = $('.js-followed-buttons')
Please register or sign in to reply