/cc @HansMuller @Hixie

Just had this problem, top SliverPadding is set to 20.0 by default. Looking at docs I see:

/// By default, [ListView] will automatically pad the list's scrollable
/// extremities to avoid partial obstructions indicated by [MediaQuery]'s
/// padding. To avoid this behavior, override with a zero [padding] property.

Yeah this is intentional. If you put a widget before the ListView, you should wrap the ListView with a MediaQuery.removePadding widget (with removeTop: true).

Well, as long as this is documented I will close the issue

I'm not sure it's well-documented yet. If you can't find it in the documentation, please don't hesitate to reopen.

I had this same issue and after some search this is the only exact answer I've found. Maybe is worth to create a short entry on documentation about window measurement and specific cases

Found this topic because I thought this is maybe a bug or I did oversee something. So maybe some more info is needed. (I would prefer a method to turn this off inside the listview, too. This would be easier.)

I did not find it in the documentation, is it there?

I assume this should not be closed because @Hixie added the d: api docs label after the issue was closed.

https://api.flutter.dev/flutter/widgets/ListView-class.html

The docs now have a comment about this behavior:

By default, ListView will automatically pad the list's scrollable extremities to avoid partial obstructions indicated by MediaQuery's padding. To avoid this behavior, override with a zero padding property.

I think it can be closed.

Yeah this is intentional. If you put a widget before the ListView, you should wrap the ListView with a MediaQuery.removePadding widget (with removeTop: true).

This solution is amazing. Thank you so much.

Yeah this is intentional. If you put a widget before the ListView, you should wrap the ListView with a MediaQuery.removePadding widget (with removeTop: true).

Thank you very much!
This code solved my problem:

Widget _myListView(){
  return MediaQuery.removePadding(
    context: context,
    removeTop: true,
    child: ListView.builder(
     .......
    )
  );
}

I do not feel the documentation is helpful. I would be lost without an example line of code.
I did this to remove all padding. Then pad each of your rows using container widget. I'm not an expert at all so please advise.
padding: const EdgeInsets.all(0.0)

We can also fix this by wrapping whole Scaffold body part in SafeArea if there is no Appbar in your screen.

return Scaffold(
      body: SafeArea(
        child: Container(
          child: ListView.builder(
          .......
          );
        ),
      ),
    );

The solution that worked for me was to set the ListView padding to zero as here

child: ListView.builder(
    padding: EdgeInsets.zero,
    itemBuilder: (context, index) {
        return Card(...);
    },
),

Most likely this is not the most recommended way, but since I can define the size of the ListView through its parent that is a Container, and the Card() widget has its own defined size. One of most likely many solutions for this problem. Felt like sharing it as none of the options above suited my situation.

Yeah this is intentional. If you put a widget before the ListView, you should wrap the ListView with a MediaQuery.removePadding widget (with removeTop: true).

Tks a lot! This applies too when we need to show one scaffold into another scaffold

Just had this problem, top SliverPadding is set to 20.0 by default. Looking at docs I see:

/// By default, [ListView] will automatically pad the list's scrollable
/// extremities to avoid partial obstructions indicated by [MediaQuery]'s
/// padding. To avoid this behavior, override with a zero [padding] property.

thanks, this work for me

This was really an unexpected implicit and hidden that made you doubt your own sanity (until adding padding: EdgeInsets.zero).

@Hixie (the guy who thought me CSS box model on Freenode IRC about 18-20yrs ago <3) :
Is this setting padding: okay or ist a wrapping in MediaQuery.removePadding(... recommended/must-have. Latter is much more code and convoluted to the uninitiated eyes.

Once you know about SafeArea it makes more sense. The problem is that in trying to make SafeArea work automatically without having to think about it, we also require that in cases where you do things it can't handle you have to handle it. I don't think we have a good solution to this other than improving the docs. If this is still confusing then we should add another section to the "troubleshooting" part of the Scaffold docs. Please do file a new bug if you'd like us to do that.

Yeah this is intentional. If you put a widget before the ListView, you should wrap the ListView with a MediaQuery.removePadding widget (with removeTop: true).

Well that was a life saver, thanks.

Yeah this is intentional. If you put a widget before the ListView, you should wrap the ListView with a MediaQuery.removePadding widget (with removeTop: true).

This solution helped me and removed my top space of GridView.builder widget:

Container(
            child: MediaQuery.removePadding(
              removeTop: true,
              context: context,
              child: GridView.builder(

Happy to get your help. Thanks dear.

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.