You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have no clue how to do a Git edit, but basically, this code fixes the issue. A little awkward but since we're looking for a case where the Next button may be either at index 0 or 1, this was all I could come up with off the top of my head.
~ Line 890
case nextPageKey:
case prevPageKey: {
const pageButtons = Array.from(document.querySelectorAll(".paginator>button"));
if (pageButtons && (document.getElementsByClassName('paginator').length > 0)) {
var myNodeList;
if (event.code === nextPageKey) {
myNodeList = document.querySelectorAll(".paginator>.btn.btn-secondary");
for (let i = 0; i < myNodeList.length; i++) {
if(myNodeList[i].textContent === "Next") {
myNodeList[i].click()
}
}
} else {
myNodeList = document.querySelectorAll(".paginator>.btn.btn-secondary");
for (let i = 0; i < myNodeList.length; i++) {
if(myNodeList[i].textContent === "Prev") {
myNodeList[i].click()
}
}
}
}
The text was updated successfully, but these errors were encountered:
This might sound pedandic, but Git has no concept of "Editing". Instead, in Git you will make a new version, and git will track the changes between one version and the next.
In order to "Edit" this file you will have to:
Create a copy of this repository on your own profile (This is called a fork)
Make the changes you want to make
Save the changes (In Git this is called committing)
Create a Pull Request to this repository
The owner of this repository will then have the chance to review your changes, and accept, reject or ask for additional changes.
OK, thanks. I'll give it a try if I get a chance. Apparently the deletion of the Back button is a permanent thing, so the solution should probably take that into account. Not to mention still being compatible with older versions that do have a back button…
I have no clue how to do a Git edit, but basically, this code fixes the issue. A little awkward but since we're looking for a case where the Next button may be either at index 0 or 1, this was all I could come up with off the top of my head.
~ Line 890
The text was updated successfully, but these errors were encountered: