[Webkit-unassigned] [Bug 271526] New: What happened to the development? Bugs are growing!

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Mar 23 14:48:36 PDT 2024


https://bugs.webkit.org/show_bug.cgi?id=271526

            Bug ID: 271526
           Summary: What happened to the development? Bugs are growing!
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: CSS
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: stevestasteislost at icloud.com

First I found a bug: https://developer.apple.com/forums//thread/745708?answerId=778577022#778577022
Then there were updates. They didn’t make anything better! Firefox stopped counting too. And Safari doesn’t even say “this CSS is invalid”, it makes it invalid (if you believe the inspector): “li: :after” comes from where?
Now I found another funny thing:
The page is a piece “holy grail”. No JS at all! The center area shows some pictures. The aside-area and the footer reside at the right and bottom border. They are “turned out” with CSS rotate. To view them and to view some bigger versions of the pictures, I did give them a tab-index. But what’s this? Tab-index is doing fine — when tabbing backwards (Shift-Tab). But it doesn’t do anything, if I try a normal, forward, Tab. After the normal Tab the page doesn’t notice Tabs any more. Neither forward, nor backwards. Even after a reload (Cmd-R) this doesn’t change. I have to close an reopen it for to see the backwards-tabbing.

Problem: the page, the CSS, is relatively complex. CSS does use CSS-nesting expensively. The sources for the mentioned effects, hovering, setting the focus and the counter-elements, are nested. It would be a hard piece of work to shrink it for an example to show here (and keep the bugs within). — Oh, one thing more: this does happen in Safari. Firefox does tabbing as expected.

I wisch, I didn’t tell you about the original bug. The answer is: more bugs!

Any suggestions?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240323/a1f8a252/attachment.htm>


More information about the webkit-unassigned mailing list