Bug 1853316 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

The issue occurs from removing `position: fixed`, which the regressing bug does. Restoring `position: fixed` or using `position: absolute` will fix the cut off.  

We have Bug 1852141 advising against using `position: fixed` due to issues with scrollbars documented in Bug 1851657 (it will behave differently for MacOS). Concerning the latter bug, it was filed when the sidebar header still had an icon, and I believe the issue improved after removing it.

I tested with the browser toolbox, and it seems that even with `position: absolute`, `position: fixed`, or neither, I can't scroll horizontally if zoomed in to the onboarding card. So, I think we can probably put back `position` if that's a quicker and easier solution for us to settle on before the end of 119? The issues with the onboarding card will need to be resolved by the onboarding team separately.
The issue occurs from removing `position: fixed`, which the regressing bug does. Restoring `position: fixed` or using `position: absolute` will fix the cut off.  

We have Bug 1852141 advising against using `position: fixed` due to issues with scrollbars documented in Bug 1851657 (it will behave differently for MacOS). Concerning the latter bug, it was filed when the sidebar header still had an icon, and I believe the issue improved after removing it.

I tested with the browser toolbox, and it seems that even with `position: absolute`, `position: fixed`, or neither, I can't scroll horizontally if zoomed in to the onboarding card. So, I think we can probably put back `position` if that's a quicker and easier solution for us to settle on before the end of 119?The issues with the onboarding card will need to be resolved by the onboarding team separately.

**Update**: we should use `position: absolute` to allow showing scrollbars. Not `fixed`.
The issue occurs from removing `position: fixed`, which the regressing bug does. Restoring `position: fixed` or using `position: absolute` will fix the cut off.  

We have Bug 1852141 advising against using `position: fixed` due to issues with scrollbars documented in Bug 1851657 (we should use `position: absolute` instead). Concerning the latter bug, it was filed when the sidebar header still had an icon, and I believe the issue improved after removing it.

I tested with the browser toolbox, and it seems that even with `position: absolute` or not, I can't scroll horizontally if zoomed in to the onboarding card. Works fine though with the main sidebar content. Therefore, we can probably use `position: absolute` if that's a quicker and easier solution for us to settle on before the end of 119? The issues with the onboarding card will need to be resolved by the onboarding team separately.

Back to Bug 1853316 Comment 2