17

In question

Relative/absolute positinging for html email in Outlook

the main issue the the floating div, which moves below the image if the view-port is large enough.

The issue is impossible to view because the code part takes up more than half the height of the screen and is exacerbated by the main container is not full height.

enter image description here

Improve this question
9
  • 3
    Correct me if I'm wrong, but expanding the snippets just made the result fullscreen before, right? Because now it seems to put the code in half the screen Commented May 16 at 12:29
  • 6
    Yes, before only the rendering was full screen. In the above example, the OP's version is hiding the white text in the small "run snippet" and moving it around - yes there are scroll bars, but that does not change that the viewport is not the full browser Commented May 16 at 12:42
  • 2
    Something to do with updates made for the Stacks Editor integration, perhaps? Commented May 16 at 18:24
  • 4
    @VLAZ I think it even specifically said "full screen" before, instead of "expand". Commented May 16 at 18:48
  • 6
    Also reported on MSO: Stack snippets are missing the Fullscreen button Commented May 18 at 13:26
  • 3
    Actually, where can we complain about this usefull "fullpage" functionnality removed from the snippets to be heard ? The expand functionnality is mainly annoying and useless to my own humble point of view. :) Commented May 29 at 13:42
  • @G-Cyrillus granted, I've used it quite rarely. But I wouldn't call it useless - it has its uses. Some times you want to see something bigger than 600x200px. Also, I don't think I'd call the functionality annoying. It only works when I explicitly want it to. It'd be annoying if it didn't. But since I can opt into when I see it, I've never experienced it when I didn't want to. Which does bring me back to using it extremely rarely. Commented May 29 at 13:56
  • 3
    @VLAZ You are right, i am actually annoyed because i am still expecting and missing the fullpage mode. ;) Commented May 29 at 14:19
  • 4
    The previous full page mode was absolutely critical for demonstrating responsive techniques. I used it a lot and many of my answers encouraged viewers to use the full page link to test the responsive behaviour. This new mode is completely useless!!!!! Commented Jun 9 at 9:55

1 Answer 1

Reset to default
10

"Full screen" snippet output/preview is now an "Expand" button that does… nothing as expected, and nothing as advertised.

  • Now, it full-screens "some code", and the output is still a merely ~300 px height area. We really needed, almost always, that extra vertical space to showcase our state-of-the-art output example, that could feature somehow all the necessary in an as-"normal"-as-possible, viewport.
    Before, the entire output preview could've been seen. (With a "Return to question" button). And it worked!
  • We don't need an ultra-wide code preview - to show the entire, well, snippet, again, in full-screen. Whilst most developers have ~2,3 columns even in their IDE anyways, and the code was already visible in the question to begin with (wrapped or not).
  • Decisions were made that in the expanded snippet we should see CSS, JS and HTML, all inside one common parent, even though the languages used cannot be written in a single document/file as previewed. At least not without placing correctly in <style> and <script>.
  • The output preview is not even visible on mobile devices (Chromium, Android)

I really thought that what I was seeing was just a joke, or an A/B/Z testing, soon to die. And that I was randomly the target of such one. This is going on for months now and it's… drainingly demoralizing, or to say, odd at least.

Regarding Stack Snippets, it's been more than a decade already for users desperately trying to:

  • Enlarge in-answer only the console output (in case where the answer was purely based on a JavaScript logic by logging to console), without relying to CSS tricks like .as-console-wrapper { max-height: 100% !important; top: 0; } Example
  • We have the "Show console" checkbox, but somehow we can't show only a specific Language pane (JS/CSS/HTML) just because the question was strictly i.e: CSS-related and what was important to showcase is, the output (obviously), plus only that single CSS fix. Or likewise, showcase only the output + some small JS fix. (UX-wise, here the reader would logically expect a "Expand all/specific pane/s" button/s, eventually, but not necessarily use them).
  • Allow the Snippets <iframe> to whitelist the Storage API. No, instead thousands of answers rely on explaining not to click the Run Code Snippet, but rather to: "go look at a bin, fiddle, whatever" external website. (To be frank I might be missing some security restrictions here, eventually).
  • A Copy button, to copy the entire code snipp... wait, we finally have that one? Seems almost unbelievable, specially given the way users coming for an answer use the site.
  • I probably missed many other wanna-have-features for Code Snippets, I believe
Improve this answer
2
  • 1
    And I can only enter a comment at the TOP of the comments, scrolling the comment I am answering off the screen, and then my comment is anyway posted at the bottom... Really anti UX Commented Jun 2 at 5:40
  • 2
    Many answerers stated specifically in their answers or comments things like: "Please, run the above snippet in "Full screen" to get a better view of the improved layout" — for example. All those hints are still in the wild - and make not much sense any more. They've become automagically legacy bloat. Worse, they might now even confuse a viewer expanding that thing. Commented Jun 2 at 6:55

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.