Are the png, webp, etc. Panes still necessary, when pn.pane.Image can accommodate these formats? about panel

[jbednar]

The Image pane is a "macro" pane that select one of the other more-specific image panes to do the actual work (whichever one first recognizes this particular image). So those other panes are still necessary, as currently implemented.

If we want to reduce the visible API surface, we could probably find a way to hide those panes from the Component Gallery top-level listing, making them reachable only via the Image pane. But that could confuse anyone looking for info on e.g. the SVG pane in particular, so I'm not sure it's necessarily a net win. So I'm neutral (neither for nor against) that idea.

[Coderambling]

Hm I see. That makes sense. Maybe add your sentence below to the Image pane doc for clarity?

"The Image pane is a "macro" pane that selects one of the other more-specific image panes to do the actual work (whichever one first recognizes this particular image)."

[Coderambling]

Made PR to add that sentence to docs:

#6904

[Coderambling]

2nd PR to update docs: #7004