Can't see autocomplete (emoticons or mentions) in replies
-
Start a new post
Type
:
, I get the autocomplete popup.
Type@
I get the autocomplete popup.REPLY to a post
Type
:
, no popup
Type@
, no popupPS: Chrome Version 55.0.2883.87 m (64-bit) so pre-emptive "fuck you" to FF22 blame.
-
Oh this is extra fucking rich.
Reply to THIS post, type
@
, and the popup is halfway down the screen. I assume there's some css dumb-shittery going on that's pushing the autocomplete off the screen in some cases?
-
Scroll all the way to the bottom of this post.
Click reply.
Type
@
. No popup.
-
Scroll all the way down.
Click "Reply"
Type
@
, no popup.Delete the
@
.Scroll to the TOP of the page.
Type
@
Popup.
Fucking hell, NodeBB.
-
BUG REPORT: scrolling makes the
position: absolute;
dropdown box move around the page
RESOLVED FIXED: changedposition: absolute;
toposition: fixed;
BUG REPORT: scrolling down before opening the dropdown box makes it appear further down the page based on how far the user has scrolled down.
-
@ben_lubar This further cements my resolve that anyone using
position:fixed
for anything is doing it wrong and needs to stop doing whatever they are doing.
-
@Lorne-Kates said in Can't see autocomplete (emoticons or mentions) in replies:
@ben_lubar This further cements my resolve that anyone using
position:fixed
for anything is doing it wrong and needs to stop doing whatever they are doing.fixed
is the correct position here, I think, they just need to set the menu'stop
correctly.
-
@Lorne-Kates said in Can't see autocomplete (emoticons or mentions) in replies:
anyone using
position:fixed
for anything except title bar on top of pages is doing it wrong and needs to stop doing whatever they are doing.IMO, there's one exception for that. But yeah, given how the browsers implement position:fixed using it for anything else is .
-
@CreatedToDislikeThis said in Can't see autocomplete (emoticons or mentions) in replies:
@Lorne-Kates said in Can't see autocomplete (emoticons or mentions) in replies:
@ben_lubar This further cements my resolve that anyone using
position:fixed
for anything is doing it wrong and needs to stop doing whatever they are doing.fixed
is the correct position here, I think, they just need to set the menu'stop
correctly.If it is fixed in the wrong place, because the right place can't actually be calculated, is
fixed
truly "correct"?
-
@cheong said in Can't see autocomplete (emoticons or mentions) in replies:
IMO, there's one exception for that.
I have my guess, but curious what your "exception" is.
-
@Lorne-Kates The words I added to quoted paragraph.
-
@cheong said in Can't see autocomplete (emoticons or mentions) in replies:
@Lorne-Kates The words I added to quoted paragraph.
To make it simpler, I've highlighted them in this screenshot:
-
@Lorne-Kates said in Can't see autocomplete (emoticons or mentions) in replies:
so pre-emptive "fuck you" to FF22 blame.
pfff you are no fun
-
@Lorne-Kates said in Can't see autocomplete (emoticons or mentions) in replies:
Start a new post
Type
:
, I get the autocomplete popup.
Type@
I get the autocomplete popup.REPLY to a post
Type
:
, no popup
Type@
, no popupPS: Chrome Version 55.0.2883.87 m (64-bit) so pre-emptive "fuck you" to FF22 blame.
Fuck you FF22 lolz
Filed under: let's not allow facts to spoil the fun!
-
@cheong said in Can't see autocomplete (emoticons or mentions) in replies:
@Lorne-Kates The words I added to quoted paragraph.
You expect me to read what you wrote?
Also, you are wrong. I fucking hate fixed-top titlebars. Because 99.999999% of them take up at least 25% of the screen, which cuts down on my already limited vertical real-estate. I don't need shit floating overtop of what I'm reading. Especially when I scroll down, and the line I last read goes behind the titlebar. Normally I'd just scan the top line at the top of the browser window to see where I am. Not anymore. Now I need to look at the top of the browser window, realize that isn't the top of the page, then look down to find where the top line is. It breaks muscle memory. Therefore it is bad.
Also it breaks in-page searching, since if the word you're looking for is behind the floating header, you will never see it highlight.
And if I want something in the header, I'll press HOME or CTRL-PGUP. I have never once needed something in the header when I was mid-page.
It's why my most common Stylish userstyle is in the form of
head, header, .header, #header, .fixed-head { position: static !important }
Filed under: <a href="#>Yes, even here
-
@Lorne-Kates said in Can't see autocomplete (emoticons or mentions) in replies:
hate fixed-top titlebars.
Now that you mention it, I'm wondering why it's not doing the needful and small-izing itself when in twilight-mode:
Edit: Ooops, wrong screenshot:
-
I removed code and now it works better.
Here's a lesson, kids: don't override defaults just because you can.
-
@Lorne-Kates Well, I have no problem of it when the designers remembered to put corresponding "padding-top" to BODY selector of the stylesheet.
But yeah, I DO hate titlebar that take away 25% of the screen. Usually a floating button that offer to "return to top" is good enough.
-
@cheong said in Can't see autocomplete (emoticons or mentions) in replies:
@Lorne-Kates Well, I have no problem of it when the designers remembered to put corresponding "padding-top" to BODY selector of the stylesheet.
But yeah, I DO hate titlebar that take away 25% of the screen. Usually a floating button that offer to "return to top" is good enough.
Ah, but in the case of infiniscroll this often leads to not going to the top, but actually just going so far and making the last "page" of posts load in instead.
-
-
@CreatedToDislikeThis said in Can't see autocomplete (emoticons or mentions) in replies:
@Lorne-Kates said in Can't see autocomplete (emoticons or mentions) in replies:
@ben_lubar This further cements my resolve that anyone using
position:fixed
for anything is doing it wrong and needs to stop doing whatever they are doing.fixed
is the correct position here, I think, they just need to set the menu'stop
correctly.I believe that
absolute
would be preferable. The problem is that the autocomplete elements are essentially siblings of the composer control when they should be descendants of it. With the element hierarchy that is in place, there isn't really a "great" solution.
-
@abarker
absolute
only works when it's the child of descendent ofrelative
, otherwise it'll be absolute relative to the body element. Either way, it's subject to moving when you scroll, whichfixed
isn't, as that is relative to the window, not the document.Besides, the issue isn't
fixed
vsabsolute
: the issue is the auto-complete always appears below, even when there isn't room.
-
@RaceProUK said in Can't see autocomplete (emoticons or mentions) in replies:
@abarker
absolute
only works when it's the child of descendent ofrelative
Not quite.
absolute
positions an element relative to the last non-static ancestor. That could be an ancestor which is positionedfixed
,absolute
, orrelative
. (example)@RaceProUK said in Can't see autocomplete (emoticons or mentions) in replies:
otherwise it'll be absolute relative to the body element
Correct, the body is the default if all ancestors are positioned statically.
@RaceProUK said in Can't see autocomplete (emoticons or mentions) in replies:
Either way, it's subject to moving when you scroll, which fixed isn't, as that is relative to the window, not the document.
That depends on what it is positioned relative to. If the auto-complete dropdown were
absolute
and a descendant of the composer area, it would not change position when the thread is scrolled. Depending on exactly how the structuring was done, it might change position based on the scrolling of the editor, but that might be considered desireable UI because it would keep the dropdown next to the point of insertion.But because the auto-complete elements are not descendents of the composer, all that goes out the window. You can't easily keep the dropdown near the point of insertion (especially since every dropdown has a unique ID). Any changes in window size completely screw you over. And so on.
-
@abarker I see.
After a quick experiment with Chrome's dev tools, it looks like the dropdown can be moved into the composer element and set to
absolute
without breaking anything. That will fix the scrolling-with-body issue properly, and make solving the appear-out-of-frame issue easier to solve (I think).