stereobooster/react-snap

Third party-requests with inlineCss enabled shows up as 400 error

Open

#219 opened on Jul 22, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (4,982 stars) (403 forks)batch import
bughelp wanted

Description

Reproducible example: repo.

Initially bug reported here https://github.com/stereobooster/react-snap/issues/217

Contributor guide

Tech stack
javascriptreact
Domain
frontendperformance
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
React basicsUnderstanding of static prerendering
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the reproducible example repo linked in the issue (https://github.com/stereobooster/an almost static stack/tree/400 error react snap) and the original bug report (https://github.com/stereobooster/react snap/issues/217). Determine if the 400 error is caused by third party requests when inlineCss is enabled. Check the react snap codebase for how inlineCss is handled and if there are any known issues with external resources.