You say it was blocking, but as said avast doesn't block, it scans and alerts to infection, it isn't its intention to specifically block as it isn't a firewall.
So there has to be some sort of interaction going on to stop the eula pop-up (this interaction wouldn't happen with no shields), there is presumably some sort of script to pop-up that eula screen. I don't know what browser you were using (?) if that had pop-up blocking enabled or an add-on to block pop-ups and these might have some interaction. Whilst this interaction is going on, somehow the pop-up either fails or times out, so it doesn't get displayed.
By disabling all of the shields (aside from a risk, especially on a public wifi), you aren't narrowing it down to see where that interaction might lie. Because I believe there is some sort of script involvement to display the pop-up, the avast script shield may have an interaction (so I would have started with disabling the script shield). If that didn't work the next area would be Web Shield as that has a direct interaction in that your browser's http traffic is redirected through the web shield proxy. The web shield doesn't monitor any https (secure encrypted traffic/protocol), so switching between http and https pages would be an area to investigate.
Obviously no one can physically check this out for you to see A) the source code of the initial page, B) the URLs of the pages involved and C) how the eula pop-up is called (if there is any switching from http to https and possibly back to http connections). We would have to be in the restaurant trying to connect to the public wifi to be able to determine the above.