Alexandre.Gagnon

@NancyMcCallB I tried to use the `FloatingViewportContent` as a drop-in replacement for the `ViewportComponent` but our code requires that we grab the viewport ref. I wasn't able to do that...

> I was wondering if we shouldnt just pass in the viewState through for FloatingViewport, but we sadly need the viewstate resolved for the processViewSelectorChange... Right. My main concern is...

> > here is the screenshot of the compatibility checker. > > Did you change your browser to use your GPU? Because @a-gagnon's screenshot shows software rendering and "major performance...

@pmconne You can refer to the [following sandbox](https://www.itwinjs.org/sandboxes/gagnon-a/issue-zoom-to-elements) for an example. I cut a lot of corners coming up with a working sandbox example, but the idea is `SpecializedViewState` display...

> Would you agree that subclassing SpatialViewState to achieve this is a pretty clumsy solution (albeit, potentially necessary due to what the current API offers)? Scene-based viewer API should address...

Reviving this PR that has more or less been put on a shelf for the past weeks.

> @a-gagnon This is old and no one approved...does it need additional update before we can complete it? Haven't played with the app since then, but those should really be...

> In 4.2.x and earlier did the terrain get greyed out like the non-emphasized elements? Pulled an back older version to create a video and I noticed the 'terrain' was...

Correct, that would be a change in widget behavior. 'Locatable: off' does not seem to fix the problem. Even when transparency is high and you would expect the hit to...

We use whatever the default is. Our tool implements `filterHit` with the list of element ids we emphasized. Normal selection tool works against desired element under normal conditions. As soon...