Skip to content

@angular/pwa noscript fallback missing #11543

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

Closed
markgoho opened this issue Jul 13, 2018 · 3 comments · Fixed by #11953
Closed

@angular/pwa noscript fallback missing #11543

markgoho opened this issue Jul 13, 2018 · 3 comments · Fixed by #11953
Labels
area: @schematics/angular freq2: medium needs: more info Reporter must clarify the issue P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful severity5: regression

Comments

@markgoho
Copy link
Contributor

Bug Report or Feature Request (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request

Area

- [X] devkit
- [ ] schematics

Versions

Repro steps

ng add @angular/pwa

Desired functionality

in the index.html file, we should see
<noscript>Please enable JavaScript to continue using this application.</noscript>

Mention any other details that might be useful

This code was merged in on May 21: angular/devkit#853 by @filipesilva but has somehow been lost in the shuffle.

@markgoho
Copy link
Contributor Author

markgoho commented Jul 13, 2018

It looks like the code is still there:

= '<noscript>Please enable JavaScript to continue using this application.</noscript>';

and the spec file:

.toMatch(/<noscript>Please enable JavaScript to continue using this application.<\/noscript>/);

However, the index.html file is not being updated with this line.

@Brocco
Copy link
Contributor

Brocco commented Jul 20, 2018

I agree that the code and test appear to be OK, perhaps it is how we are parsing the index.html file in order to determine where to place this text.

Can you please share the contents of your index.html file for testing?

Thanks!

@Brocco Brocco added the needs: more info Reporter must clarify the issue label Jul 20, 2018
@hansl hansl added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Jul 30, 2018
clydin added a commit to clydin/angular-cli that referenced this issue Aug 20, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: @schematics/angular freq2: medium needs: more info Reporter must clarify the issue P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful severity5: regression
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants