Is the SVG cursor size discernible to the site?

On Thursday, May 26, 2022 at 9:18:09 PM UTC-4 Chris Harrelson wrote:

> Hi Sahir,
>
> On Thu, May 26, 2022 at 1:44 PM 'Sahir Vellani' via blink-dev <
> [email protected]> wrote:
>
>> Platform cursor size used as default for custom SVG cursors if no 
>> specified size. SVG cursors can scale based on the platform 
>> accessibility/cursor settings. This can be overridden if the cursor has any 
>> specified dimensions. This feature is initially available on Windows only.
>>
> Could you say why? Is it hard to implement?
>  
>
>>
>>
>> Interoperability and Compatibility
>>
>> Web developers will need to reexamine the way they handle SVG cursors 
>> with no specified sizes. A custom cursor may be rendered where it was 
>> previously just the default cursor image.
>>
>
> Is it possible this will break sites? How many sites use SVG cursors right 
> now?
>  
>
>>
>> *Gecko*: No signal
>>
>> *WebKit*: No signal
>>
>
> What do Gecko and Webkit do at the moment?
>  
>
>>
>> *Web developers*: No signals
>>
>> *Other signals*:
>>
>> WebView application risks
>>
>> Does this intent deprecate or change behavior of existing APIs, such that 
>> it has potentially high risk for Android WebView-based applications?
>>
>>
>>
>> Debuggability
>>
>>
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac, 
>> Linux, Chrome OS, Android, and Android WebView)?
>> No
>>
>> Is this feature fully tested by web-platform-tests 
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ?
>> No
>>
>> Flag name
>>
>> Requires code in //chrome?
>> False
>>
>> Tracking bug
>> https://bugs.chromium.org/p/chromium/issues/detail?id=737459
>>
>> Estimated milestones
>>
>> 105
>>
>>
>> Anticipated spec changes
>>
>> Open questions about a feature may be a source of future web compat or 
>> interop issues. Please list open issues (e.g. links to known github issues 
>> in the project for the feature specification) whose resolution may 
>> introduce web compat/interop risk (e.g., changing to naming or structure of 
>> the API in a non-backward-compatible way).
>>
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5112911184789504
>>
>> This intent message was generated by Chrome Platform Status 
>> <https://chromestatus.com/>.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b87b0ab4-836d-45f0-af04-2ce26b3e718an%40chromium.org
>>  
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b87b0ab4-836d-45f0-af04-2ce26b3e718an%40chromium.org?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/dfb7dc58-6d3e-4ea2-9f1c-86837afa3becn%40chromium.org.

Reply via email to