Thanks for wanting to do a PR, @VinShen !

We try to merge all non-breaking bugfixes and will deliberate the value of new features for the community. Please note there is no guarantee your pull request will be merged, so if you want to be sure before investing the work, feel free to contact the team first.

@igotinfected

Personally, this doesn't seem like a bug to me but rather the correct and expected behavior. The fact that it worked the way YOU expected in v6 was likely just a lucky coincidence. Since the entire thing is inside the ActivatorContent, I would expect the entire component to open the picker when you click anywhere within its area, pixel by pixel. It shouldn't know or care about the filter header or anything else.

Yeah with v7 the file upload component was rewritten for multiple reasons like accessibility, HTML semantics, complexity, usability etc., this was just a side effect of the previous implementation where the ButtonTemplate acted more as a wrapper + button template.

I don't see any way to replicate the same behaviour other than potentially rendering the fileupload manually over just_ the rows, though with this approach (and the one you have right now) you're already losing out on row click features, are you not?

@igotinfected
@ScarletKuro

Thanks for you reply.

I am developing a advanced Web File Manager with MudBlazor using MudTreeView, MudTable, MudFileUpload etc.

In MudBlazor 6.x.x using
MudTable as File Explorer to show Folders and Files. Also using Drag and Drop files to add files.
Entire MudTable inside MudFileUpload
There is separate button (outside this MudFileUpload+MudTable) for uploading File which uses other MudFileUpload component.
Drag and Drop on MudTable works properly.
Achieveing row ('Name') click feature using MudElement inside MudTd 'Name' - File Picker is not opened when clicked on MudElement.
Click on MudTableSortLabel in HeaderContent, MudTablePager everything works without opening the File Picker.
I may be lucky to achieve everything required in MudBlazor 6.x.x.
Attached images of MudBlazor 6.x.x.

In MudBlazor 7.x.x
I could achieve everything above, except click on MudTableSortLabel in HeaderContent, MudTablePager where File Picker gets opened.
Though not entire row, but I could achieve row ('Name' column) click feature using MudElement inside MudTd.
Attached images of MudBlazor 7.x.x.

I ported complete Application from MudBlazor 6.x.x to 7.x.x, but can't switch to, because of this File Picker opening.
So I am stuck up.

I wish that the Drag and Drop should work without opening the File Picker on click on MudFileUpload component.
Can I disable opening of File Picker on MudFileUpload when used for Drag and Drop using InputClass or any flag?

Is there any way I can achieve this from .razor or programmetically using MudBlazor 7.x.x.?

Please suggest.

Thanks

@VinShen I copied your code from the original snippet and ran it locally using 6.21.0 (replaced ActivatorContent with ButtonTemplate and removed z-10 class from MudFileUpload).

The areas surrounded by red do not activate the file picker:

By adding a div with stopPropagation and preventDefault around your table you can achieve the same effect (try.mudblazor.com snippet):

<div @onclick:stopPropagation
     @onclick:preventDefault>
     ...
</div>

Could you try that and let me know?

@igotinfected

Excellent solution.

Everything works as expected (no File Picker) except a small issue in MudTablePager First, Previous, Next, Last buttons, where File Picker opens on click. Please check in snippet sent by you.

May be in future, it will be better, to provide a flag to disable opening of File Picker (when clicked on drop zone) in MudFileUpload when used specifically for Drag and Drop. In Drag Drop mode opening of File Picker every time on click is irritating.

Thanks a lot for your help.

@VinShen hmm weird, I'll check when I get home in a few hours.

I think the "file drop zone only" logic can be useful in scenarios such as yours. I might look into a decent way to implement it provided the team thinks it should be part of the core component.

@VinShen a bit of special case with the new way MudFileUpload works, will be "fixed" with #9626 for the time being but the solution I've provided may not be supported in the future. Will still look into a drop zone only component over the next days :)

@igotinfected

Any updates regarding "file drop zone only" implementation discussion with Team and #9626 fix?

@VinShen been busy with the fulltime job but I'll try to put some time aside over the weekend for it!

@igotinfected

Tried Version v7.7.0 - No changes in MudFileUpload. I am still using Version 6.21.0

Any updates regarding "file drop zone only" implementation discussion with Team and #9626 fix?

@VinShen
I had this same problem and managed to fix it by wrapping the button (table in your case) in the following to essentially disable the file picker activation that gets applied to the nested buttons:

<CascadingValue Value="@((IActivatable)null!)">
  <MudTable>
    ...
  </MudTable>
</CascadingValue>

Unfortunately the @onclick:stopPropagation @onclick:preventDefault solution didn't seem to work on the latest MudBlazor version.

Obviously as @ScarletKuro mentions this is now not the intended way to use this now but in our case it has worked and will allow us to upgrade to v7