Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Why did default CSS behavior for a nested/child element change from "initial" to "inherit" after update?

  • 4 odgovori
  • 0 ima to težavo
  • 11 ogledov
  • Zadnji odgovor od antizilla

more options

I updated from version 106 to version 118.0.2, then to 119.0.1. The last to updates made a local HTML page behave differently than before.

The problem is this: the "inside text" below was not(!) bold before the update, I suppose the containing element of the text defaulted to "initial," but began to default to "inherit" after the update.

This is HTML:

  <TABLE>
    <TR>
      <TD class="group">
        outside text
        <TABLE>
          <TR>
            <TD>
              inside text
            </TD>
          </TR>
        </TABLE>
      </TD>
    </TR>
  </TABLE>

This is external CSS linked to the page:

 TD.group
   { font-weight:bold;
   }

So I added "TD.group TABLE{font-weight:initial;}" to the CSS to make it work as expected/before.

I wonder why this change was made by the developers, Did I miss any changes made to HTML/CSS specification?

Thank you

I updated from version 106 to version 118.0.2, then to 119.0.1. The last to updates made a local HTML page behave differently than before. The problem is this: the "inside text" below was not(!) bold before the update, I suppose the containing element of the text defaulted to "initial," but began to default to "inherit" after the update. This is HTML: <pre><nowiki> <TABLE> <TR> <TD class="group"> outside text <TABLE> <TR> <TD> inside text </TD> </TR> </TABLE> </TD> </TR> </TABLE> </nowiki></pre> This is external CSS linked to the page: TD.group { font-weight:bold; } So I added "TD.group TABLE{font-weight:initial;}" to the CSS to make it work as expected/before. I wonder why this change was made by the developers, Did I miss any changes made to HTML/CSS specification? Thank you

Spremenil cor-el

Izbrana rešitev

OK, I forgot to test with <!DOCTYPE> html and in that case the inside text is bold. I think that this always has been the case.

data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+CjxodG1sPgo8aGVhZD4KPHN0eWxlPnRkLmdyb3Vwe2ZvbnQtd2VpZ2h0OmJvbGR9PC9zdHlsZT4KPC9oZWFkPgo8Ym9keT4KPFRBQkxFPgogICAgPFRSPgogICAgICA8VEQgY2xhc3M9Imdyb3VwIj4KICAgICAgICBvdXRzaWRlIHRleHQKICAgICAgICA8VEFCTEU+CiAgICAgICAgICA8VFI+CiAgICAgICAgICAgIDxURD4KICAgICAgICAgICAgICBpbnNpZGUgdGV4dAogICAgICAgICAgICA8L1REPgogICAgICAgICAgPC9UUj4KICAgICAgICA8L1RBQkxFPgogICAgICA8L1REPgogICAgPC9UUj4KICA8L1RBQkxFPgo8L2JvZHk+CjwvaHRtbD4=

Preberite ta odgovor v kontekstu 👍 0

Vsi odgovori (4)

more options

You can run mozregression between versions 106 and 119 to find the change responsible.

more options

Seems to work fine for me. data:text/html;charset=utf-8;base64,PHN0eWxlPiB0ZC5ncm91cHtmb250LXdlaWdodDpib2xkfSA8L3N0eWxlPgo8VEFCTEU+CiAgICA8VFI+CiAgICAgIDxURCBjbGFzcz0iZ3JvdXAiPgogICAgICAgIG91dHNpZGUgdGV4dAogICAgICAgIDxUQUJMRT4KICAgICAgICAgIDxUUj4KICAgICAgICAgICAgPFREPgogICAgICAgICAgICAgIGluc2lkZSB0ZXh0CiAgICAgICAgICAgIDwvVEQ+CiAgICAgICAgICA8L1RSPgogICAgICAgIDwvVEFCTEU+CiAgICAgIDwvVEQ+CiAgICA8L1RSPgogIDwvVEFCTEU+

more options

Izbrana rešitev

OK, I forgot to test with <!DOCTYPE> html and in that case the inside text is bold. I think that this always has been the case.

data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+CjxodG1sPgo8aGVhZD4KPHN0eWxlPnRkLmdyb3Vwe2ZvbnQtd2VpZ2h0OmJvbGR9PC9zdHlsZT4KPC9oZWFkPgo8Ym9keT4KPFRBQkxFPgogICAgPFRSPgogICAgICA8VEQgY2xhc3M9Imdyb3VwIj4KICAgICAgICBvdXRzaWRlIHRleHQKICAgICAgICA8VEFCTEU+CiAgICAgICAgICA8VFI+CiAgICAgICAgICAgIDxURD4KICAgICAgICAgICAgICBpbnNpZGUgdGV4dAogICAgICAgICAgICA8L1REPgogICAgICAgICAgPC9UUj4KICAgICAgICA8L1RBQkxFPgogICAgICA8L1REPgogICAgPC9UUj4KICA8L1RBQkxFPgo8L2JvZHk+CjwvaHRtbD4=

more options

zeroknight, cor-el, thank you for responding.

cor-el, removing the DOCTYPE did it. I must've added it to the page at some point to avoid Firefox generating the warning and never thought of testing it (due to being absolutely sure that it won't break anything). Thank you.