You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Sven Meier <sv...@meiers.net> on 2015/12/06 10:17:02 UTC
cors attribute
Hi,
I've noticed that the "crossorigin" attribute is popping on several
places now:
- Image
- ExternalImage
- MediaComponent
The first two share the enumeration, the latter has its own inner enum.
Since CORS seems to be a general topic, why not move the enum into its
own file? Writing of the attribute could be moved to a behavior, making
this completely transparent for the components.
WDYT?
Sven
Re: cors attribute
Posted by Tobias Soloschenko <to...@googlemail.com>.
Sounds good to me! If it is used at so many places!
kind regards
Tobias
> Am 06.12.2015 um 14:40 schrieb Sven Meier <sv...@meiers.net>:
>
> Hi Tobias,
>
> <link> has "crossorigin" too, and <script> might get it official in the future:
>
> https://developer.mozilla.org/en/docs/Web/HTML/Element/script
>
> It always has the values "anonymous" or "user-credentials". If we used a behavior to render the attribute, we wouldn't need NO_CORS any longer.
>
> Regards
> Sven
>
>
>> On 06.12.2015 12:20, Tobias Soloschenko wrote:
>> Hi Sven,
>>
>> I would suggest to externalize it and use a separate for MediaC and Image, because it might diff in feature changes. WDYT?
>>
>> kind regards
>>
>> Tobias
>>
>>> Am 06.12.2015 um 10:17 schrieb Sven Meier <sv...@meiers.net>:
>>>
>>> Hi,
>>>
>>> I've noticed that the "crossorigin" attribute is popping on several places now:
>>>
>>> - Image
>>> - ExternalImage
>>> - MediaComponent
>>>
>>> The first two share the enumeration, the latter has its own inner enum.
>>>
>>> Since CORS seems to be a general topic, why not move the enum into its own file? Writing of the attribute could be moved to a behavior, making this completely transparent for the components.
>>>
>>> WDYT?
>>>
>>> Sven
Re: cors attribute
Posted by Sven Meier <sv...@meiers.net>.
Hi Tobias,
<link> has "crossorigin" too, and <script> might get it official in the
future:
https://developer.mozilla.org/en/docs/Web/HTML/Element/script
It always has the values "anonymous" or "user-credentials". If we used a
behavior to render the attribute, we wouldn't need NO_CORS any longer.
Regards
Sven
On 06.12.2015 12:20, Tobias Soloschenko wrote:
> Hi Sven,
>
> I would suggest to externalize it and use a separate for MediaC and Image, because it might diff in feature changes. WDYT?
>
> kind regards
>
> Tobias
>
>> Am 06.12.2015 um 10:17 schrieb Sven Meier <sv...@meiers.net>:
>>
>> Hi,
>>
>> I've noticed that the "crossorigin" attribute is popping on several places now:
>>
>> - Image
>> - ExternalImage
>> - MediaComponent
>>
>> The first two share the enumeration, the latter has its own inner enum.
>>
>> Since CORS seems to be a general topic, why not move the enum into its own file? Writing of the attribute could be moved to a behavior, making this completely transparent for the components.
>>
>> WDYT?
>>
>> Sven
Re: cors attribute
Posted by Tobias Soloschenko <to...@googlemail.com>.
Hi Sven,
I would suggest to externalize it and use a separate for MediaC and Image, because it might diff in feature changes. WDYT?
kind regards
Tobias
> Am 06.12.2015 um 10:17 schrieb Sven Meier <sv...@meiers.net>:
>
> Hi,
>
> I've noticed that the "crossorigin" attribute is popping on several places now:
>
> - Image
> - ExternalImage
> - MediaComponent
>
> The first two share the enumeration, the latter has its own inner enum.
>
> Since CORS seems to be a general topic, why not move the enum into its own file? Writing of the attribute could be moved to a behavior, making this completely transparent for the components.
>
> WDYT?
>
> Sven