Note that there are some explanatory texts on larger screens.

plurals
  1. USmachineghost
    primarykey
    data
    text
    plurals
    1. CO(what I mean by "because of all the factors involved is", is that the layout of an individual element is affected by the layout of its parent, its parent's parent, its parent's parent's parent, .... plus the layout of any sibling elements, plus the layout of any child elements. A CSS style defined for any one of those could be responsible for something weird you see in the original element's layout, so it's very tricky to figure out what exactly is causing the things you see. If however you can make a simple page with just the problem elements, you can remove all those potential factors.)
      singulars
    2. COFor the IE thing you might want to try: overflow:hidden;. It's hard to say exactly what your issue is though without being able to see it (if you can expose a sample page that shows the issue on the web somewhere that'd be more helpful), but basically this just sounds like a CSS layout issue. However, because of all the factors involved, those kinds of issues can be very tricky to debug, so I'd also recommend removing as much as you can around the problem, so that you just have a page with the problem elements and nothing else. This should make isolating the problem a lot easier.
      singulars
    3. COThe problem with questions like these is that: A) They're not actually questions, B) they're so broad they're basically unanswerable, and C) Instead of feeling like "this guy is asking for help" they feel like "this guy is asking me to perfect his code so that he doesn't have to". This makes it so that there's no way for anyone to give a satisfying answer (not that anyone would want to, per C). I'd recommend modifying this post to ask a specific question (eg. "Is there a faster way to do this one loop?", NOT just "Do you have any suggestions on improving performance or readability?").
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload