Yea, My first thought where I saw the problem was to ask myself why the computed width is done server side, at least, only here.
I did the patch like this to avoid to change too greatly the behavior but I admit now that a client side will be the best.
Now the problem with JavaScript is the switch is visible when the page is loaded and there’ll be a delay before the application of the width so the resize will be visible.
The best would be a pure CSS solution but I even not sure its possible the way the switch is.
This is why I would keep a fix on the server side when loading the page. The actual server side computed width still wrong.
I’m interested to investigate for it, I just hope it will not take too much time, I already spent quite some on this.
Hi Kristina,
Yea, My first thought where I saw the problem was to ask myself why the computed width is done server side, at least, only here.
I did the patch like this to avoid to change too greatly the behavior but I admit now that a client side will be the best.
Now the problem with JavaScript is the switch is visible when the page is loaded and there’ll be a delay before the application of the width so the resize will be visible.
The best would be a pure CSS solution but I even not sure its possible the way the switch is.
This is why I would keep a fix on the server side when loading the page. The actual server side computed width still wrong.
I’m interested to investigate for it, I just hope it will not take too much time, I already spent quite some on this.
Regards,
Gilles-Philippe Leblanc