Skip to content

Conversation

@lordelix
Copy link
Contributor

Description

Call file highlighting after files are redered to view

Related Issue

Fixes #28106

How Has This Been Tested?

Visual test in FF; Chrome, IE11 and MS Edge

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@PVince81
Copy link
Contributor

This will likely re-highlight the file again every time the file list is reloaded, when navigating between folders.

I suggest setting _scrollTo to null as soon as the event has run.

@felixboehm felixboehm added this to the development milestone Aug 14, 2017
@felixboehm felixboehm added the p2-high Escalation, on top of current planning, release blocker label Aug 14, 2017
@lordelix
Copy link
Contributor Author

lordelix commented Aug 14, 2017

This will likely re-highlight the file again every time the file list is reloaded when navigating between folders.

That's true. I thought .one(… should do the trick but it didn't 👅
Anyway … updated :-)

Copy link
Contributor

@PVince81 PVince81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Please backport to stable10

@lordelix
Copy link
Contributor Author

Please backport to stable10

Never done this before. Whats the workflow?

@DeepDiver1975
Copy link
Member

Never done this before. Whats the workflow?

https://gist.github.com/DeepDiver1975/33cde0c03f0c321132ca517cc5fbd580

@DeepDiver1975
Copy link
Member

but first squash these commits together - THX

@phil-davis
Copy link
Contributor

phil-davis commented Aug 14, 2017

@DeepDiver1975 has his own magic script, but the process is:

  • find the commit-id SHA in the list of commits in master (after the main PR to master has been squash-merged...) - there is a button to "Copy the full SHA" which is easy
git checkout stable10
git checkout -b stable10-fh_fix_permalink
git cherry-pick <commit-id>
git push

then go to GitHub make a PR from that branch, making sure to select stable10 as the to which to make the PR to.

Hmmm - @deep got there first.

@lordelix lordelix merged commit 9514a97 into master Aug 15, 2017
@lordelix lordelix deleted the fh_fix_permalink branch August 15, 2017 07:57
@lordelix
Copy link
Contributor Author

@PVince81 backport: #28681

@lock
Copy link

lock bot commented Aug 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

3 - To Review p2-high Escalation, on top of current planning, release blocker status/STALE

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Permalink to files in subfolders doesn't point to the file.

7 participants