You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Base Porting Checklist
- [x] Component/package name (`CommunityToolkit.WinUI.Extensions`)
- [x] Namespace `CommunityToolkit.WinUI`
- [x] Merge differences from UWP main to WinAppSDK / Uno forks
- [x] Import original doc or setup new doc
- [ ] Needs a refresh/update, and probably split
- [x] Samples
- [ ] Tests
- [ ] All brought over tests pass for UWP/WinAppSDK
- [ ] https://github.com/CommunityToolkit/Windows/issues/134
- [x] Support for WASM via Uno Platform
## Notable Changes
- [ ] For FrameworkExtensions, look at https://github.com/CommunityToolkit/Labs-Windows/blob/main/components/SegmentedControl/src/Helpers/FrameworkElementExtensions.cs. Some changes were made that to trigger the extension upon loading.
@niels9001 originally we did a big push in 7.0 to flatten the namespace and remove 'extensions' so they were all consistent across the package for easy usage.
We could have the component/package maybe be called Extensions if we change the scope of what's inside it, but may want to think about still having a base namespace for some of these things?
@michael-hawker Yeah, if we went back and added "Extensions" back it'd be a bit weird.
FWIW we also don't use "Extensions" in the .NET Community Toolkit.
Looking at the template that Niels copied I think he may have just used Namespace to mean package/component name? But will clarify in a quick-sync tomorrow. 🙂
Haha, yeah, I guess that line was a bit more specific to the Converters as they are in their own namespace anyway. (Maybe that's a separate discussion as to if they should remain there.)
Anyway, all good. We'll sort it out and can update these issues all together at our next sync.
#4 also needs the WeakEventListener and DispatcherQueue extensons. So we should port those over as well into the general base helpers/extensions place.
Should we have the extensions and helpers together as like a common folder/component name?
I believe the top two work differently in UWP vs. WinAppSDK, so probably need to look at more closely if it makes sense to have them. Also, I believe @niels9001 has some thoughts about Titlebar helpers in general we should investigate for a revamp, especially with the platform doing work to better enable custom titlebars, see microsoft/microsoft-ui-xaml#8137
The Middle Click Scrolling extensions are dependent on Windowing APIs, Input APIs, and Cursor APIs, which all work very differently between UWP and Windows App SDK, so not porting for now, as I don't think they work for Windows App SDK at the moment, so probably need more attention.
With WebView2 now, we should figure out if we need to remap these extensions or how that should work.
Activity
michael-hawker commentedon Mar 21, 2023
@niels9001 originally we did a big push in 7.0 to flatten the namespace and remove 'extensions' so they were all consistent across the package for easy usage.
Context:
We could have the component/package maybe be called
Extensionsif we change the scope of what's inside it, but may want to think about still having a base namespace for some of these things?@Sergio0694 thoughts?
Sergio0694 commentedon Mar 21, 2023
Heyoooooo I see a new repo 👀👀👀
@michael-hawker Yeah, if we went back and added "Extensions" back it'd be a bit weird.
FWIW we also don't use "Extensions" in the .NET Community Toolkit.
michael-hawker commentedon Mar 22, 2023
Looking at the template that Niels copied I think he may have just used
Namespaceto meanpackage/componentname? But will clarify in a quick-sync tomorrow. 🙂niels9001 commentedon Mar 22, 2023
@Sergio0694 @michael-hawker Oh yeah, I basically just replaced the last bit of namespace from the previous template. So please ignore / update 😄!
michael-hawker commentedon Mar 22, 2023
Haha, yeah, I guess that line was a bit more specific to the
Convertersas they are in their own namespace anyway. (Maybe that's a separate discussion as to if they should remain there.)Anyway, all good. We'll sort it out and can update these issues all together at our next sync.
michael-hawker commentedon Mar 22, 2023
#4 also needs the WeakEventListener and DispatcherQueue extensons. So we should port those over as well into the general base helpers/extensions place.
Should we have the extensions and helpers together as like a
commonfolder/component name?michael-hawker commentedon Mar 22, 2023
We have some extensions in the base
Microsoft.Toolkit.Uwppackage merging those in with the extensions ofMicrosoft.Toolkit.Uwp.UIpackage here.Then will create a separate
Helperscomponent I think that contains most of the rest?michael-hawker commentedon Mar 22, 2023
Currently have not brought over:
I believe the top two work differently in UWP vs. WinAppSDK, so probably need to look at more closely if it makes sense to have them. Also, I believe @niels9001 has some thoughts about Titlebar helpers in general we should investigate for a revamp, especially with the platform doing work to better enable custom titlebars, see microsoft/microsoft-ui-xaml#8137
The Middle Click Scrolling extensions are dependent on Windowing APIs, Input APIs, and Cursor APIs, which all work very differently between UWP and Windows App SDK, so not porting for now, as I don't think they work for Windows App SDK at the moment, so probably need more attention.
With WebView2 now, we should figure out if we need to remap these extensions or how that should work.
hoshiizumiya commentedon Jan 10, 2026
https://github.com/CommunityToolkit/Windows/blob/main/components/Extensions/src/ScrollViewer/ScrollViewerExtensions.Properties.cs

For ScrollViewerExtensions.EnableMiddleClickScrolling, it doesn't exist.