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

Added referrer policy support to GUI Image to control xhr request header #12664

Merged
merged 5 commits into from
Jun 22, 2022

Conversation

BrunevalPE
Copy link
Contributor

This feature will allow user's to control the header in the xhr request to load the image, Referrer Policy.

More info here :
The Referrer-Policy HTTP header

Default value is : strict-origin-when-cross-origin

@azure-pipelines
Copy link

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

@azure-pipelines
Copy link

There is no need to update the "what's new.md" file. A changelog will be generated using the PR and its tags.

@azure-pipelines
Copy link

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

@azure-pipelines
Copy link

@azure-pipelines
Copy link

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

@azure-pipelines
Copy link

@sebavan sebavan requested a review from RaananW June 20, 2022 14:59
@sebavan
Copy link
Member

sebavan commented Jun 20, 2022

Adding @RaananW as a reviewer who is way more versed that I am on this part :-)

I love the overall idea but wonder about persistence as well as should we do it for the 3d textures and much more ?

Copy link
Member

@RaananW RaananW left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's more of a question of whether or not this is the right place for this.

We already have Tools.SetCorsBehavior, which changes the crossOrigin of the specific request/image. We also have the WebRequest modifiers to change any request made ourside of a simple image load. This feels like a 3rd way to solve a similar issue.

I like the idea of adding it, but we need to find a global way to be able to set this. Only in the GUI is probably not suffecient.

packages/dev/gui/src/2D/controls/image.ts Outdated Show resolved Hide resolved
@BrunevalPE
Copy link
Contributor Author

Hello ! I'm not sure for the serialization, so I removed it, I will put it back if you think it's relevant.
I don't want to consume memory on Image instances so I changed it to be nullable and not forcing the default state.
Tools seems to be a better place for this code, indeed 👍

@azure-pipelines
Copy link

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

@azure-pipelines
Copy link

Copy link
Member

@RaananW RaananW left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@sebavan, any objection merging this?

@sebavan sebavan merged commit 08b2276 into BabylonJS:master Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants