Improve reliability of scrollUnderFloatingHeader

[labkey-tchad]

Rationale

With just the right window size, the domain designer floating header blocks the field collapse button in such a way that ScrollUtilscrollUnderFloatingHeader doesn't detect it.

org.openqa.selenium.ElementClickInterceptedException: Element <span class="fa fa-lg fa-chevron-down"> is not clickable at point (125,2) because another element <div class="domain-field-row domain-row-border-default domain-floating-hdr"> obscures it
[...]
  at app//org.labkey.test.selenium.WebElementWrapper.click(WebElementWrapper.java:37)
  at app//org.labkey.test.selenium.ReclickingWebElement.click(ReclickingWebElement.java:74)
  at app//org.labkey.test.selenium.WebElementWrapper.click(WebElementWrapper.java:37)
  at app//org.labkey.test.components.domain.DomainFieldRow.collapse(DomainFieldRow.java:272)
  at app//org.labkey.test.components.domain.DomainFormPanel.editField(DomainFormPanel.java:256)
  at app//org.labkey.test.components.domain.DomainFormPanel.addField(DomainFormPanel.java:104)
  at app//org.labkey.test.tests.luminex.LuminexGuideSetDisablingTest.init(LuminexGuideSetDisablingTest.java:92)
  at app//org.labkey.test.tests.luminex.LuminexGuideSetDisablingTest.initer(LuminexGuideSetDisablingTest.java:82)

Making the floating header check a bit more lenient fixes this problem for me locally.

Related Pull Requests

• N/A

Changes

• Improve reliability of scrollUnderFloatingHeader

[labkey-tchad]

Verifying on TeamCity: https://teamcity.labkey.org/buildConfiguration/LabkeyTrunk_ModuleSuites_LuminexPostgres/3799230