Ehren
Invision Community Team
-
Joined
-
Last visited
-
Dreadknux reacted to a comment:
Design Bug: Images Within Wrap-In Box Adds Padding + Background Color
-
Fine with me! 😅 -
-
That’s definitely the intention. I’ll look into it today 🤝
-
-
-
Just a friendly bump @Dreadknux . If you have a URL I can check, that would be great! 👍
-
-
-
-
First issue is now fixed. Thanks!
-
Apologies, I didn't realse you'd be testing the ACP too. The ACP requires a different code change. The one I provided is for the front-end. There are 4 instances of body:has() in the CSS. I've removed all 4 for the update. This is a notable one from the ACP: body:has(#acpLiveSearchResults:not([style*="block"])) .acpSearch__close{}
-
-
Sure. This code was removed from 4-mobile-footer.css in favour of a different solution. body:has(.ipsEditor:focus-within) .ipsMobileFooter{ transform: translateY(100%); }
-
The second bug was fixed last week, but likely didn't make it in time for the final release. I'll look into the first one for you now 🤝
-
I wasn't able to naturally reproduce this on any of my devices, however I've now been able to by throttling Chromes CPU by 20x, which makes it run very slow. The culprit was a CSS selector, and surprisingly not a JS issue as some have speculated. It's likely a result of poor implementation of the :has() selector in Chrome. The tooltips now appear instantly for me when using a throttled version of Chrome. Before/after videos are below, and the fix should hopefully arrive in the next update if testing goes well 🤝 Screen Recording 2025-03-26 at 9.43.14 am.mov Screen Recording 2025-03-26 at 9.42.40 am.mov
-
I've just tested Edge on iOS 18.3.2 and the editor is working for me. Does the same issue happen with Safari? If so, and if you have access to a Mac, you can inspect the website to see if there are any console errors. It might be as simple as a cached file. Does the issue happen in a private tab?
-
Changed Status to Not a bug
-
The validator only tests for "CSS Level 3" code. Those alerts are all valid pieces of code and are understood by all modern (and not so modern) browsers.
-
Changed Status to Not a bug
-
Hello, Similar to the other W3C bugs, none of this code is invalid. The validator is testing for "CSS Level 3" code, but all of this is beyond that. The first line just changes the value depending on if light or dark mode is used. The validator doesn't understand color-mix, which is causing this alert. The validator doesn't understand container queries, causing this alert. Again, the validator doesn't understand color-mix Not a bug 🙂
-
Changed Status to Not a bug
