Skip to content

Commit f4bfeac

Browse files
committed
docs: update README for Content Security Policy directives formatting
1 parent 0514cc7 commit f4bfeac

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

packages/browser-sdk/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -387,11 +387,11 @@ Types are bundled together with the library and exposed automatically when impor
387387

388388
If you are running with strict Content Security Policies active on your website, you will need to enable these directives in order to use the SDK:
389389

390-
| Directive | Values | Reason |
391-
| ----------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
392-
| connect-src | [https://front.reflag.com](https://front.reflag.com) | Basic functionality` |
390+
| Directive | Values | Reason |
391+
| ----------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
392+
| connect-src | [https://front.reflag.com](https://front.reflag.com) | Basic functionality` |
393393
| connect-src | [https://livemessaging.bucket.co](https://livemessaging.bucket.co) | Server sent events for use in automated feedback surveys, which allows for automatically collecting feedback when a user used a flag. |
394-
| style-src | 'unsafe-inline' | The feedback UI is styled with inline styles. Not having this directive results unstyled HTML elements. |
394+
| style-src | 'unsafe-inline' | The feedback UI is styled with inline styles. Not having this directive results unstyled HTML elements. |
395395

396396
If you are including the Reflag tracking SDK with a `<script>`-tag from `jsdelivr.net` you will also need:
397397

0 commit comments

Comments
 (0)