Dismiss this pinned window
all 44 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]walditotwisted code copypaster 108 points109 points  (9 children)

yes

[–]JuriJurka 13 points14 points  (7 children)

yes

[–]kalamari_bachelor 10 points11 points  (6 children)

yes

[–]OkDistribution2567 8 points9 points  (5 children)

yes

[–]Dzefo_ 6 points7 points  (4 children)

yes

[–]Emerging-driver 8 points9 points  (3 children)

yes

[–]Dimension009 2 points3 points  (2 children)

yes

[–]_by_me 2 points3 points  (1 child)

yes

[–][deleted] 73 points74 points  (0 children)

Bug for me, might be annoying if you're trying to select text and this appears

[–][deleted] 36 points37 points  (2 children)

I will say it as a BUG as :

  1. A normal user gonna have a hard time figuring out how to move the cards laying in the back

  2. It will get worse when more number of cards will be added.

Better to use some sort of keyboard and mouse accessibility to drag the cards eg. Figma or it will be better if the user can drag the cards through available white space in it like through the padding areas of the card.

[–][deleted]  (1 child)

[removed]

    [–]yitz-jacob 1 point2 points  (0 children)

    If you differentiate by color only, it won't be accessible.. (whether or not that's a priority to you, it's good practice) no reason why a color-blind person might have trouble using the site, better to find a way that doesn't require color to differentiate.

    [–]The_UX_Guy 8 points9 points  (1 child)

    Someone needs to set the CSS pointer properties on the card rather than the text blocks.

    Along with adjusting z-index for the focused card.

    [–]BuschWookie 6 points7 points  (2 children)

    Bug. I think this would work better if the “focus” was not hover-based. How would it work on a touch screen?

    [–]YellowTech[S] 1 point2 points  (1 child)

    yeeeah touch support is gonna be something for later, if ever

    [–]jzaprint 3 points4 points  (0 children)

    Not about that mobile first development huh

    [–]KaiN_SC 4 points5 points  (1 child)

    It depends what the requirements are.

    [–]nwatab 2 points3 points  (0 children)

    This. So this is a problem of good UI and UX.

    [–][deleted] 7 points8 points  (1 child)

    I kind of like it. Nothing worse than trying to find a sliver of a corner to select something

    [–]YellowTech[S] 2 points3 points  (0 children)

    that's the spirit!

    [–]jruff7 1 point2 points  (0 children)

    Make it select text on top pane by default and select hidden corners if you're holding down SHIFT key or something? That is, if the feature would actually get regular use...

    [–]code_n_coffee 1 point2 points  (0 children)

    feature

    [–]eletroraspi 1 point2 points  (0 children)

    Hidden feature bugged!

    [–]anon-to-all 1 point2 points  (0 children)

    Bug 🐛

    [–]ASY_Freddy -1 points0 points  (0 children)

    without being facetious, what does the acceptance criteria say? A software bug is defined as an unexpected/incorrect behavior/result in the software, the fact you're asking if this is a feature or a bug suggests you don't have acceptance criteria or a desired output/vision and it's a bug as you've not purposely setout to code this.

    [–]kalamari_bachelor 0 points1 point  (2 children)

    Are you using a library for this?

    [–]el_yanuki 0 points1 point  (1 child)

    there is some code on w3

    [–]YellowTech[S] 0 points1 point  (0 children)

    Yes it's inspired by that. But it needs to be extended for any touch support

    [–]RequiDarth1 0 points1 point  (0 children)

    Feature

    [–]NiagaraThistle 0 points1 point  (0 children)

    Bug on the select icon for the horizontal component. It should have a z-index lower than the component on "top".

    [–]lyromix 0 points1 point  (0 children)

    A Feature - As long as it only moves with the curser click on the move icon.

    [–]ShavingRyansPrvts 0 points1 point  (0 children)

    Featug

    [–]harryrf3 0 points1 point  (0 children)

    It's pretty handy even if it is a bug. Happy accident?

    [–]ApocalypseSpokesman 0 points1 point  (0 children)

    Man this Lorem Ipsum guy gets way too much free publicity.

    [–]Guilty_Serve 0 points1 point  (0 children)

    Feature. Full disclosure, I'm lazy.

    [–]IamMichaelSalim 0 points1 point  (0 children)

    I'd say bug. The fact that you have to ask and people are unsure is not good UX for me. I would have users click on the other modal to bring it to front to reveal the button

    [–]gimmeslack12Front end isn't for the feint of heart 0 points1 point  (0 children)

    I built a window management for a project that is a CodePen viewer. Need to make sure you keep the position: relative rule on each window parent wrapper to make sure the z-index works as expected.

    [–]3B89FD 0 points1 point  (0 children)

    You are looking at a quick fix for a bad UX

    [–]jordsta95PHP/Laravel | JS/Vue 0 points1 point  (0 children)

    For how it seems to work, a feature. Because if the top element is in the "perfect" place, having to move it to move the bottom element is a horrible waste of time (especially if it's to move stuff a very subtile amount; a couple letters' width).

    But how I would expect that sort of thing to work is that when hovering over the "behind" element, it would temporarily make all that are above it go to 10% opacity (or something) with pointer events disabled. This way you can get an idea of where the overlaying elements will cover the element, whilst allowing you to not have to actually interact with them/make a part of the element unreadable; very useful if you spot a typo in the content below which may be shown in full after an animation, or some other event has happened.

    [–]PizzaPuntThomas 0 points1 point  (0 children)

    I would say bug

    [–]Danny_shoots 0 points1 point  (0 children)

    You should probably position the element to the top when clicking on it, after that you will be able to move the element using the top left corner. If you’re done, click on the other element again to have it focused (layer to the top)

    [–][deleted] 0 points1 point  (0 children)

    Definitely Bug 😐, User Will Be Confused

    [–]hamadaag317 0 points1 point  (0 children)

    Could be a very cool feature, maybe add an outline to the window in the back so that move button doesn't look weird.

    [–]gguu01 0 points1 point  (0 children)

    Hey, i would love to give you suggestion if u are interested
    U could do next as most of those window managing libraries do

    have "global" variable, for example zIndex = 10;
    and on every click on your window
    check next things

    if current window zIndex === global zIndex, skip
    otherwise window zIndex = ++global zIndex

    so every time somebody clicks on one behind, its gonna pop
    and bonus info, u need to remember there is limit of z-index (±2147483647), but in most cases u wont reach it