This method is called when the selection geometry changes, this include scrolling a scrollable with an existing selection. The selected content can be the same in this case.

Hey, thanks for the review :). Could you please elaborate on this case with a small example code? I tried putting a text in scrollable but could not replicate this behavior that is, the method was not called while scrolling.

try this

import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: SelectionArea(
        child: Scaffold(
          appBar: AppBar(title: const Text(_title)),
          body: Center(
            child: ListView.builder(
              itemBuilder: (BuildContext context, int index) {
                return Text('text $index');
              },
              itemCount: 1000,
            ),
          ),
        ),
      ),
    );
  }
}

select something and scroll

There is also some concern about calling getSelectedContent in this method since it can be called every frame when scrolling and the getSelectedContent does a tree walk.

I tried your code on chrome but got the same results. I also tried running it on my android phone and got the same result there. Am I missing something? 🤔

I've just changed this and I get the "update" output only when I select text or change the selected text 🤔

ah I see, just scroll back and forth without scroll the selection off screen. because once it is offscreen the method wouldnt be call

Same result :( Tried scrolling back and forth a few times, keeping it on the edge and scrolling with different speeds as well. Couldn't replicate it neither on chrome nor on my phone.

This is getting more and more mysterious, I can reproduce it. Do you have the latest master branch? when you test it on mobile, does the toolbar move around when you scrolling? because it relies on this method to update its position

Yes, I'm running on the latest master just pulled it a while ago. Here is how it looks on my phone, it just gives the update message only when a selection changes.

Will this be called if the user just taps various locations in the text? I wonder if it's changing an invisible collapsed selection in those cases.

This will only be called when an existing selection changes in value. So, if the user just taps on various locations, it would just call this only once when the selection becomes empty, and then it would remain silent until an actual selection is made.