Making a live site is non-trivial for me. Unfortunately, i am not aware of how to recplicate it within a codepen.
However, the sample project is literally just the default quasar init project with a modified index.vue and a footer added the layout. There is very little there. On Thu, Jan 17, 2019 at 1:24 PM Simon Fraser <simon.fra...@apple.com> wrote: > On Jan 17, 2019, at 4:57 AM, Eric Gorr <ericg...@gmail.com> wrote: > > I have a (fairly) simple, sample project at: > > > https://github.com/EricG-Personal/quasar_tab_layout/tree/feature/scroll_area_only > (note, this is the feature/scroll_area_only branch) > > which demonstrates the problem. If the project is built and run, it the > content in the scroll area renders correctly in the latest, released > version of Firefox, but not in the latest, released version of Safari. > > The project is based on quasar (https://quasar-framework.org) and to get > it up and running should be easy: > > (equivalent NPM commands can also be used) > > 1. yarn global add vue-cli > 2. yarn global add quasar-cli > 3. git clone https://github.com/EricG-Personal/quasar_tab_layout.git > 4, cd quasar_tab_layout > 5. git checkout feature/scroll_area_only > 6. quasar dev > > The general structure is scroll area->Inner Div->Content Container > DIV->Content Div’s … It’s the Inner Div whose height is 0. The height of > the Content Container DIV is correct and seems to be calculated based on > the total height of the Content Div’s. When the height of the scroll area > is explicitly set, the Inner Div gets the same height at the scroll area > When the height of the scroll area is calculated automatically, the Inner > Div does not receive the height of the scroll area (However, with the > latest version of Firefox, the Inner Div does get the height of QScrollArea > and that would seem is why it works.) > > I am not sure if this is a quasar framework bug or a browser bug. As near > as I can tell my code is correct and the content of the scroll area and was > hoping someone here could help me eliminate it or confirm as a webkit bug > which may need to be reported and fixed. > > > Could you put up a live site (or make a CodePen or something) that shows > the bug? > > Simon > > >
_______________________________________________ webkit-help mailing list webkit-help@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-help