Thanks for reporting. I was afraid a breaking change like that would happen eventually 😞

For everyone affected: It is possible, to use the forceApply flag in the polyfill config to provide your own feature-detection until the polyfill is released with adjusted default feature detection.

The current code is

mobile-drag-drop/src/internal/feature-detection.ts

Lines 15 to 23 in d1abdd5

    
           const isBlinkEngine = !!((<any>window).chrome) || /chrome/i.test( navigator.userAgent ); 
        
           features.userAgentSupportingNativeDnD = !( 
        
               // if is mobile safari or android browser -> no native dnd 
        
               (/iPad|iPhone|iPod|Android/.test( navigator.userAgent )) 
        
               || // OR 
        
               //if is blink(chrome/opera) with touch events enabled -> no native dnd 
        
               (isBlinkEngine && ("ontouchstart" in document.documentElement)) 
        
           );

Relates to #152

	const isBlinkEngine = !!((<any>window).chrome) \|\| /chrome/i.test( navigator.userAgent );

	features.userAgentSupportingNativeDnD = !(
	// if is mobile safari or android browser -> no native dnd
	(/iPad\|iPhone\|iPod\|Android/.test( navigator.userAgent ))
	\|\| // OR
	//if is blink(chrome/opera) with touch events enabled -> no native dnd
	(isBlinkEngine && ("ontouchstart" in document.documentElement))
	);

Does not automatically apply in iOS/iPad 15 when desktop website is requested #167

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions