Description of the need
When adding a context by path, every field available to the context is presented in the dialog box. This not only produces un-necessary clutter but creates a bad UX because the field chosen may be attached to a different entity type, making it easy to accidentally add a similarly named field that won't display data as expected because it doesn't belong to the given layout path provided in the context.
Additionally, not filtering on a given criteria might also a performance hit on larger sites that have hundreds of fields. By limiting through the selection rule, it reduces the number of fields that need to be loaded.
Proposed solution
Add Selection Rules so a context can be limited to only show the fields related to the rule.
Alternatives that have been considered
See the Drupal Panels module Selection Rules for more inspiration.
Recent comments
@indigoxela - I agree, I mentioned the SVG topic specifically for the dev meeting. I think we'll definitely want Nate involved in that discussion. Good call!
Apr 18th Weekly Meetings
Hi colbyat, re display in the browser: the problem is that when a 500 occurs, this PHP process died before being able to render anything. So that won't work. Logging is possible, but...
Displaying 500 errors
SVG's are a great topic for the design meeting, but also for the dev meeting. Two currently active issues related to SVG overlap a bit when it comes to security aspects. https://...
Apr 18th Weekly Meetings