admin.widgets.RelatedFieldWidgetWrapper.get_context() bypasses the used renderer

[Jacob Rief]

In django.contrib.admin, ForeignKey and ManyToManyField are mapped to a admin.widgets.RelatedFieldWidgetWrapper. This wrapper widget then renders the underling widget using:

def get_context(self, name, value, attrs):
    ...
    context = {
       "rendered_widget": self.widget.render(name, value, attrs),
        ...
    }
    ...

If the RelatedFieldWidgetWrapper itself has been rendered using an alternative renderer, the underling widgets will be rendered using the default renderer instead of the alternative renderer as used to render the said wrapper widget. This may lead to unexpected output.

Possible solution:

By adding the optional argument renderer to the get_context()-method, the widget rendering function could be rewritten as self.widget.render(name, value, attrs, renderer=renderer).

This issue might be related to #34257.

[Sarah Boyce]

Thank you for the report! This makes sense to me but might be a little fiddly to resolve

[Ahmed Nassar]

✅ Update on RelatedFieldWidgetWrapper Renderer Fix

I have submitted a PR to ensure RelatedFieldWidgetWrapper.get_context() correctly respects the provided renderer.

🔹 Fixes:

Added an optional renderer parameter.
Ensured the underlying widget uses the correct renderer.
Maintained full backward compatibility.
All tests passed successfully.

📌 The PR is ready for review. Let me know if any changes are needed!

🔗 PR: ​https://github.com/django/django/pull/19271