Skip to content

Conversation

@ZeroX-DG
Copy link
Member

@ZeroX-DG ZeroX-DG commented Jun 5, 2018

The disappearing scroll bar bug is extremely annoying and has been reported here: https://issuehunt.io/repos/53266139/issues/1632

After working on my personal project, I have found a fix for this issue.

This is bug exists due to the style of the scroll bar of codemirror, instead of applying for just codemirror, it applied to the whole window, everything that has its scroll bar unstyled. So the solution is to override that style!

@sosukesuzuki sosukesuzuki added the awaiting review ❇️ Pull request is awaiting a review. label Jun 6, 2018
@sosukesuzuki sosukesuzuki self-requested a review June 6, 2018 01:23
@Rokt33r
Copy link
Member

Rokt33r commented Jun 8, 2018

@ZeroX-DG Could you attach a screenshot after the fix?

@ZeroX-DG
Copy link
Member Author

ZeroX-DG commented Jun 8, 2018

No problem.

BEFORE:

peek 2018-06-08 18-13

AFTER:

peek 2018-06-08 18-15

@sosukesuzuki
Copy link
Member

I think that it is not bad at present..
What is the problem of the current one?

@ZeroX-DG
Copy link
Member Author

@sosukesuzuki As you can see the current scroll bar will disappear after a short period of time and only reappear if you resize the app or focus on a text box and hit the page up or page down key. The new one make sure that the scroll bar will never disappear.

@sosukesuzuki
Copy link
Member

@ZeroX-DG I know. However, I think that we are not in trouble. Why are you troubled?

@sosukesuzuki sosukesuzuki added awaiting changes 🖊️ Pull request has been reviewed, but contributor needs to make changes. and removed awaiting review ❇️ Pull request is awaiting a review. labels Jun 11, 2018
@ZeroX-DG
Copy link
Member Author

I started to think this is not related to codemirror but instead electron? I've removed codemirror scroll addon and the problem is still persist and also I've found the same issue on Atom github page: atom/atom#15107 , but it seem that their solution is just like me. But how can you guys don't experience this issue? I experienced this issue on both Boostnote and my side project which is fixed by using the traditional way to create scroll bar.

@Rokt33r
Copy link
Member

Rokt33r commented Jun 26, 2018

Hmm @sosukesuzuki For me, it looks a problem to be fixed. I'll review this.

@Rokt33r Rokt33r requested review from Rokt33r and removed request for sosukesuzuki June 26, 2018 19:51
@Rokt33r Rokt33r added awaiting review ❇️ Pull request is awaiting a review. and removed awaiting changes 🖊️ Pull request has been reviewed, but contributor needs to make changes. labels Jun 26, 2018
@Rokt33r
Copy link
Member

Rokt33r commented Jun 27, 2018

@ZeroX-DG How can I reproduce this problem? It works fine for me.
screen shot 2018-06-27 at 14 55 28

@ZeroX-DG
Copy link
Member Author

Hey @Rokt33r , why your scroll bar is the default scroll bar of chrome? Mine is not!
Here is how you can reproduce the problem:

  1. Open something long enough to make the scroll bar appears (the interface setting tab for example)
  2. Wait for it to disappear
    peek 2018-06-27 13-00

@Rokt33r
Copy link
Member

Rokt33r commented Jun 27, 2018

I'll try again.

@Rokt33r
Copy link
Member

Rokt33r commented Jun 27, 2018

Hmm.. mine never disappear... Do you have any clue why it doesn't happen to me? Btw, I didn't configure my scroll. I assume the reason might be that I'm running windows via Parallels.

@ZeroX-DG
Copy link
Member Author

I have no idea what's happening but I think if your scroll bar is still the default one then it will not disappear, do you have a linux machine to test it? Maybe it's a linux problem?

@ZeroX-DG
Copy link
Member Author

ZeroX-DG commented Jul 2, 2018

@Rokt33r I've just updated to the latest version of Boostnote (0.11.7) and the scroll bars became the default scroll bar of chrome (just like what you have) and it doesn't disappear anymore??? I gonna have to investigate the commit that change the scroll bar, but that's also means the issue is now solved, the scroll bar doesn't disappear anymore, now it just looks ugly and that's a different issue. Should we close this pull request?

@Rokt33r
Copy link
Member

Rokt33r commented Jul 3, 2018

Close this issue because the problem is suddenly gone after v0.11.7.

@Rokt33r Rokt33r closed this Jul 3, 2018
@Rokt33r
Copy link
Member

Rokt33r commented Jul 3, 2018

Reopen because it fixes other problem.

@Rokt33r Rokt33r merged commit aebed4a into BoostIO:master Jul 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting review ❇️ Pull request is awaiting a review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants