# Move hide preview button to line between composer and preview

**URL:** https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048
**Category:** UX
**Created:** [2017年十一月22日 00:55 UTC](https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048 "2017-11-22T00:55:43Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![barryvan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barryvan/32/82635_2.png) [@barryvan](https://meta.discourse.org/u/barryvan)
#### Post date: [2017年十一月22日 00:55 UTC](https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048/1 "2017-11-22T00:55:43Z")

</div>

> [@Help us test a new composer style](https://meta.discourse.org/t/help-us-test-a-new-composer-style/74552/10):
>
> I made “hide preview” grey to de-emphasize it. There is a fair bit more blue now with the blue bar, so we risk burying the blue reply button which is the primary action … there’s no way “hide preview” needs to be full blue drawing all that attention to itself, as we’ve definitely used up our blue ink attention budget.

I wonder if the “hide preview” text could actually be hidden entirely, in favour of a tall thin button between the composer and the preview; something like this, perhaps?

 ![image](https://global.discourse-cdn.com/meta/original/3X/8/a/8a878b91d7e5b14fdcb343a9c997dc39305007e1.png)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2017年十一月22日 01:01 UTC](https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048/2 "2017-11-22T01:01:48Z")

</div>

> [@Help us test a new composer style](https://meta.discourse.org/t/help-us-test-a-new-composer-style/74552/12):
>
> f the “hide preview” text could actually be hidden entirely, in favour of a tall thin button between the composer and the preview; something like this, perhaps?

Adding more bright blue is definitely not a good idea IMO. And adding a dynamic preview resize bar is out of scope for what we’re doing here, that would be a fairly major feature to add, that we’ve never had.

I think if preview is going to float with a transparent / clear background, having the text there explaining what it is, and acting as a toggle, is quite important.

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2017年十一月22日 01:03 UTC](https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048/3 "2017-11-22T01:03:27Z")

</div>

> [@Help us test a new composer style](https://meta.discourse.org/t/help-us-test-a-new-composer-style/74552/16):
>
> And adding a dynamic preview resize bar is out of scope for what we’re doing here, that would be a fairly major feature to add, that we’ve never had.

I like @barryvan’s suggestion. I don’t believe he was suggesting a resizable preview area, just replacing the text “hide preview” with a button in the middle. Could be grey/black if blue is too much.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2017年十一月22日 01:04 UTC](https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048/4 "2017-11-22T01:04:37Z")

</div>

Yes, but that’s still a sizable change, we’re mostly looking at cosmetics at this time, and as I already said

> [@Help us test a new composer style](https://meta.discourse.org/t/help-us-test-a-new-composer-style/74552/16):
>
> I think if preview is going to float with a transparent / clear background, having the text there explaining what it is, and acting as a toggle, is quite important.

In general it _is_ a good idea to remove text we have to translate, whenever we can, but I don’t think so in this particular specific case, at least not right now.

---

<div class="post-metadata">

### Author: ![barryvan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barryvan/32/82635_2.png) [@barryvan](https://meta.discourse.org/u/barryvan)
#### Post date: [2017年十一月22日 01:05 UTC](https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048/5 "2017-11-22T01:05:45Z")

</div>

> [@Help us test a new composer style](https://meta.discourse.org/t/help-us-test-a-new-composer-style/74552/16):
>
> Adding more bright blue is definitely not a good idea IMO. And adding a dynamic preview resize bar is out of scope for what we’re doing here, that would be a fairly major feature to add, that we’ve never had.

The bright blue was just a placeholder – I’d likely make this thinner, grey, and with a nicer icon. 😉 And it shouldn’t be resizable – just a collapser. Something along these lines is probably a bit more subtle:

 ![image](https://global.discourse-cdn.com/meta/original/3X/d/1/d16924a95464567efb64b57192f16b4c175404c7.png)

> [@Help us test a new composer style](https://meta.discourse.org/t/help-us-test-a-new-composer-style/74552/18):
>
> Yes, but that’s still a sizable change

Not overly so, I think – it’s mainly changing the location of the “hide preview” link in the DOM, and some minor CSS styling. 😉

From a user’s perspective, though, it is quite a large change, because rather than things just looking a little prettier, things will _move_ – and so there could be some initial confusion.

---

<div class="post-metadata">

### Author: ![notriddle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/notriddle/32/133055_2.png) [@notriddle](https://meta.discourse.org/u/notriddle)
#### Post date: [2017年十一月22日 01:36 UTC](https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048/6 "2017-11-22T01:36:47Z")

</div>

Separating the preview from the text box with a line doesn’t have to imply putting a button on that line.

 ![image](https://global.discourse-cdn.com/meta/original/3X/3/6/36c61df0f6fbb0b9255c825e2f17f35339fc0c45.png)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2017年十一月29日 22:35 UTC](https://meta.discourse.org/t/move-hide-preview-button-to-line-between-composer-and-preview/75048/7 "2017-11-29T22:35:11Z")

</div>

In my opinion this adds a fair bit of new complexity to the composer, and the marginal benefit of slightly less translated text – since we already have that text area reserved at the bottom – is not worth it.

It’s arguably a worse UI, since the words are fairly clear and help identify the floating area on the right. Take that away and you make the UI less clear. What _is_ that area on the right?

In summary, I would be quite opposed to this change.
