Bug or Feature? Not sure

  • Resolved WebSprite

    (@contentsprite)


    10 months ago

    This is a minor thing, but the fact that the notification bubble is almost always showing 1 issue is annoying. Within a few minutes of successfully manually regenerating critical CSS, the warning “We noticed you’ve recently published a new post on your site that may affect its HTML/CSS structure” shows up and the notification bubble lights up with 1 issue.

    I’ve done as little as changed an underlying link in an old post and the warning and notification bubble come back. That has nothing to do with critical CSS.

    It seems that the plug-in isn’t scanning for changes relevant to CSS but for any change of any kind regardless of how minor, then *ping* bubble is back as is suggestion that I regenerate critical CSS. It seems counter-intuitive to regenerate it multiple times a day or after every time I make a minor edit. I only want a warning bubble when there’s actually an issue.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Pete (a11n)

    (@dilirity)

    10 months ago

    Hello there!

    You’re absolutely right. The way we detect changes to Pages/Posts could be improved and I’ve opened an enhancement request on GitHub here and will discuss it with the team.

    However, though it may seem simple, it’s actually very context sensitive. As I’ve outlined in the ticket, we need a better way of detecting where changes to the content were made and how much of an impact they have on the actual elements for which Critical CSS is generated.

    Cheers!

    Floris

    (@florismk)

    8 months, 2 weeks ago

    Pinging this, as I also experience this issue: unnecessary notification bubbles for Jetpack Boost that persist after I’ve rebuilt the critical css.

    • This reply was modified 8 months, 2 weeks ago by Floris. Reason: Switched on notification
    Plugin Support Paulina H. (a11n)

    (@pehaa)

    8 months, 1 week ago

    Thank you for reporting that you experience the same issue, @florismk. This thread is already linked from the GitHub issue, so your input is taken into account in our discussions and planning. Thank you!

    Thread Starter WebSprite

    (@contentsprite)

    6 months, 1 week ago

    Circling back on this and wondering if some kind of tweak might be in the works soon? It’s as if the settings are the exact reverse of what they need to be. Resize a jpg, get a bubble warning to regenerate CSS.

    I just updated my page builder, theme, Jetpack itself, cacheing plug-in, and purged all caches, including CSS.

    No bubble.

    Plugin Support Alin (a11n)

    (@alinclamba)

    6 months ago

    Hi @contentsprite,

    Thank you for following up and for providing more details on the notification bubble’s behavior. We understand now that the issue presents a level of inconsistency—appearing too frequently for minor changes, yet not showing up for significant updates.

    We want to let you know that we’re still actively working on resolving this matter. The inconsistency you’ve highlighted is crucial for us to understand the full scope of the issue, and we’re digging deeper to ensure a more reliable and accurate notification system in future updates.

    Keep in touch!

    Plugin Support Alin (a11n)

    (@alinclamba)

    6 months ago

    Hi @contentsprite,

    Thank you for your continued feedback. To better address the inconsistency with the notification bubble, could you please provide examples of instances where you expected the regeneration notice to appear after significant updates but did not observe it? Specifically, we’re interested in learning more about the types of changes you consider significant and any common factors or conditions present when the notification fails to show up. Your input will greatly assist us in refining the notification system for future updates. Looking forward to your response.

    Best regards,

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Bug or Feature? Not sure’ is closed to new replies.