You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2022. It is now read-only.
While testing MWF 1.3.0 beta, I noticed inconsistent results using the override library between JavaScript and PHP. When I use Firefox or Safari (desktop) to goto a page:
index.php?override=basic
JavaScripts calls inside the index.php will return the expected classification. For example:
Looks like a JS bug probably caused by a partial merge. (Note to self: Do tons of frequent tiny merges rather than a mega-merge once in a while.) Should have it fixed soon.
Somehow, my cherry-pick resulted in a merge. Uh, fortunately, it's all stuff we should push to the next beta or rc or whatever anyway. You should be able to pull from master or from develop and this issue will be resolved.
Somehow, my cherry-pick resulted in a merge. Uh, fortunately, it's all
stuff we should push to the next beta or rc or whatever anyway. You
should be able to pull from master or from develop and this issue will be
resolved.
Reply to this email directly or view it on GitHub: #141 (comment)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While testing MWF 1.3.0 beta, I noticed inconsistent results using the override library between JavaScript and PHP. When I use Firefox or Safari (desktop) to goto a page:
JavaScripts calls inside the
index.php
will return the expected classification. For example:However, PHP calls inside
index.php
is not returning the expected classification. For example,As a result, the Firefox or Safari browsers are still getting the full classification of CSS and JavaScript from MWF.
The text was updated successfully, but these errors were encountered: