Ext.NET icon indicating copy to clipboard operation
Ext.NET copied to clipboard

Fieldset title blank in Chrome 87

Open fabriciomurta opened this issue 5 years ago • 4 comments

Found: 5.3.0 Ext.NET Forums' thread: FieldSet-Title in Chrome 87

With Chrome 87 launch, the Fieldset title no longer works as expected. I is simply hidden, leaving a blank space where it should have been displayed.

In Sencha Talk it was suggested that this could address the issue:

.x-fieldset-header > .x-fieldset-header-text {
    position: unset
}

This won't though, address the issue when the fieldset has the collapsible setting enabled. The title itself is displayed with the fix above, but the collapse/expand handle won't be shown.

The following stackoverflow discussion offered another solution that would work with collapsible fieldsets, but the title was hid once the field is collapsed: Problem Fieldset label not visible with Sencha ExtJs 7.x on chrome 87.0.4280.67

So the problem remains until deeper investigation can take place. There have been reports even Ext JS 6 (Ext.NET 4) was subject to this issue. In fact the issue is reproducible in Ext.NET 3 (Ext JS 5.x, example), but works normally with Ext.NET 2 (Ext JS 4.x, example).

fabriciomurta avatar Nov 23 '20 22:11 fabriciomurta

Looks like the following override fixes the problem.

.x-fieldset {
    overflow: unset;
}

overflow: hidden is set in theme-base, so it probably effects all themes.

ozguruysal avatar Nov 24 '20 10:11 ozguruysal

Thanks, @ozguruysal! I tried so many combinations and selectors that I missed the simple ones. I confirm it works with that override.

fabriciomurta avatar Nov 24 '20 19:11 fabriciomurta

Just tested with latest chromium build and the issue is still reproducible there.

It already reads as fixed so chrome 88 will probably come without the issue. We should wait before making the fix in Ext.NET.

Some likely chromium issues logged in which Chrome 87 introduced problems, that can potentially fix this:

The following issue seemed, by the date and how it affects the new version, to be the one that introduced this problem, but although this might be included in latest Chromium build, I tested it and the issue is still there.

fabriciomurta avatar Nov 24 '20 19:11 fabriciomurta

Sencha support's answer mentioned in the Stackoverflow thread you linked above seems like a good fix. See here.

ozguruysal avatar Nov 25 '20 18:11 ozguruysal