Just a small question. In the split screen preview mode (F12), I find the default size of the preview pane a little small and like to size it up. However, when you close the preview pane, and open it again, it reverts to the original size. Is there some way to get it to remember my preference?

Not yet, I have made the same recommendation to CC to put that into the new release. But as for this moment, you have to re-size it every-time.

The issue here is, what if you have 15 pages open and each as the Split Screen Preview enabled. How do you want that to work under this situation?

David - What build # are you on? I just tried it on mine, using several tabs, and EACH tab re-opened to the same size that that particular tab had been opened to. The only time it reverted back to "default" size, was if I closed the tab, re-opened that file, then opened the split screen preview.

Honestly, this is exactly how I'd expected it to work.

I prefer external preview F11. Once sized stays the same.

Keith

I have updated to the latest build (412) now as I was a few builds behind.

Oddly, I find that if I resize the preview pane, and hit F12 twice, it disappointingly reverts to the original size. But if I resize the preview pane, change tab, and then change back to the original tab, the preview pane starts defaulting to whatever size I set it to before I changed tab.

Evidently, it is almost doing what it should do, but it would be nice if it remembered the preview pane size for a given tab without having to change tab!

I also think the external preview should minimise when you hit F11, to make it easier to switch between code and external preview!

Yep, something slipped backwards between build 411 and 412 concerning the F12 preview pane sizing. It WAS holding the custom sizing (on ALL tabs) when you opened & closed the views. Now it seems it can only handle doing it with ONE tab, and even after that tab is closed, none of the others will hold the sizing.

Scott... Please see what changed on this.

I just tested this in our internal build 413 and it appears to be fixed. I will roll that update out next week as it includes a few fixes that JoAn posted as well.

You da man Scott!!! Thanks