Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notification of legacy browse #7303

Merged
merged 3 commits into from Apr 29, 2019

Conversation

capilkey
Copy link
Contributor

Original PR is here, #7295.

There was an issue where adding the meteor block to package.json caused the client/compatibility directory to no longer be included. We use that directory to hold our old JS files that don't have module support and can't be imported. The additional commit moves the JS files to the public directory and adds them to the main HTML page. The legacy browser still tries to load those files and they sometimes throw exceptions, but it's not a functional issue.

One additional thing that is now required is that the five JS files have no cache busting so I added ?v=VERSION values so that we can substitute in the client version to bust the cache like we do in the Flash client.

@antobinary
Copy link
Member

Are the VERSION substrings to be overwritten during packaging?

@antobinary antobinary merged commit 7a389ad into bigbluebutton:master Apr 29, 2019
@ffdixon ffdixon changed the title Legacy browser support take 2 Notification of legacy browse Apr 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants