in reply to Re: [OT] Testing race conditions in web pages
in thread [OT] Testing race conditions in web pages

I can easily imagine some dynamically generated CSS that depends on user settings. Getting a race condition in place in such a situation doesn't feel too far-fetched for me.

Of course, you might consider dynamically generated CSS resources weird, but I don't think that that's a problem that would only occur with PHP.

  • Comment on Re^2: [OT] Testing race conditions in web pages

Replies are listed 'Best First'.
Re^3: [OT] Testing race conditions in web pages
by 1nickt (Canon) on Dec 04, 2018 at 14:17 UTC

    Well. True, I haven't encountered dynamically-generated CSS, and I do think it is a little weird, but I suppose there are uses for such a technique. I was just kidding about blaming PHP, though!

    (edit: I have certainly manipulated CSS using JS, after page load ... and Corion reminds me that this very site generates CSS dynamically at least part of the time.)


    The way forward always starts with a minimal test.
Re^3: [OT] Testing race conditions in web pages
by Jenda (Abbot) on Dec 05, 2018 at 14:07 UTC

    Even if the CSS is indeed dynamically generated and user dependent, the race condition still makes no sense. Unless of course he's crazy enough to keep the URL of the CSS static and generate CSS for the last person that requested the page or something similarly insane.

    Jenda
    Enoch was right!
    Enjoy the last years of Rome.

      Well, not to claim that this is sane, but you could serve different CSS to different clients based on the cookie they request the URL with...

      Given the poor information the OP has shared, I think that the only way to interpret this "race condition" is that the friend is serving resource's URL(s) which maintain the whole request state consistent if they are hit in some defined consecutive and predictable order, which given the distributed nature of the HTTP protocol he should not assume.