-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime styling sometimes doesn't take effect #4738
Comments
Ah - the problem here is that Replacing |
There's an actual bug here too, however. Consider the following execution sequence:
And then the following (in independent relative ordering):
If the old property definition depended on attributes that aren't present in the new data -- for example, if the property value is a categorical source function where the source domain values are unique feature IDs -- then the result will fall back to default values (e.g. black color). |
@anandthakker Can you take a look at this? I am finding it difficult to see any easy fix without large scale refactoring (#2291, #4875), so that #3692 is feasible. |
@jfirebaugh until we can take on the necessary refactoring to solve the problem more systematically, a temporary measure to patch this would be to expose something like |
When using a GeoJSON source, and setting runtime styling properties, then updating the GeoJSON source data, the changes to the style don't always take effect.
https://jsfiddle.net/ygxuk5zy/ contains a reduced test case (replace your access token). This is how it should look:
This is how it actually looks:
The text was updated successfully, but these errors were encountered: