Status Update
No update yet.
Comments
ch...@appspot.gserviceaccount.com
I just noticed that calling .showInfoWindow() on the marker DOES place it on top of the others.
Sadly I want no info window at all. For now the trick is to create a 0px * 0px view in my own InfoWindowAdapter.
Sadly I want no info window at all. For now the trick is to create a 0px * 0px view in my own InfoWindowAdapter.
ch...@appspot.gserviceaccount.com
🥪 Regression verification projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/eccd86b3-2113-41f7-969e-6cfd776b5fd2 job 1799d882610000 for test: ChromiumPerf/mac-intel-perf/v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_avg/browse_tools/browse_tools_docs_scrolling
reproduced the regression with statistic: {'control_median': 1.0003333333333333, 'lower': 63.107816544605114, 'p_value': 1.862645149230957e-09, 'treatment_median': 1.805, 'upper': 89.22637575833112}.
Proceed to bisection.
reproduced the regression with statistic: {'control_median': 1.0003333333333333, 'lower': 63.107816544605114, 'p_value': 1.862645149230957e-09, 'treatment_median': 1.805, 'upper': 89.22637575833112}.
Proceed to bisection.
ch...@appspot.gserviceaccount.com
You can now change a Marker's icon (thanks!), however this functionality is still required!
I have tried the workaround of a 0 sized view as below, but the view actually takes up the whole width of the map and half the height (i.e. all the space above the Marker) - which stops all user interaction with the top half of the map. (If you call show then hide then the Marker is placed back to it's original z-order).
zeroSizedInfoWindow = new View(getActivity());
zeroSizedInfoWindow.setLayoutParams(new ViewGroup.LayoutParams(0, 0));
I have tried the workaround of a 0 sized view as below, but the view actually takes up the whole width of the map and half the height (i.e. all the space above the Marker) - which stops all user interaction with the top half of the map. (If you call show then hide then the Marker is placed back to it's original z-order).
zeroSizedInfoWindow = new View(getActivity());
zeroSizedInfoWindow.setLayoutParams(new ViewGroup.LayoutParams(0, 0));
ch...@appspot.gserviceaccount.com
Automatic bisection started for measurement:
ChromiumPerf/mac-intel-perf/v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_avg/browse_tools/browse_tools_docs_scrolling
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ChromiumPerf/mac-intel-perf/v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_avg/browse_tools/browse_tools_docs_scrolling
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ch...@appspot.gserviceaccount.com
[Comment deleted]
ch...@appspot.gserviceaccount.com
Is it possible to know if this issue is being solved ? I really need to set z-orders of some markers, and I can't use the infoWindow trick as I want 4 markers to be always above 4 others markers.
Thanks...
Thanks...
ch...@appspot.gserviceaccount.com
I too want to show certain markers on top of others such that if there are two types of markers Red and Blue, i want the Red marker to stay above of Blue marker.
bl...@google.com
I'm using the following workaround to add a "current selection" red marker that is always on top of another map marker (in my case, a bus stop) with the exact same lat/long, much like Google Maps does (see screenshot).
// Reduce focus marker latitude by small amount to ensure it is always on top of the
// corresponding stop marker (i.e., so its not identical to stop marker latitude)
LatLng latLng = new LatLng(stop.getLatitude() - 0.000001, stop.getLongitude());
Marker mCurrentFocusMarker = mMap.addMarker(new MarkerOptions().position(latLng));
When you slightly reducing the latitude of the marker you want on top, Google Maps will then render this marker on top of other marker.
But, it would be nice to have official z-order rending control via an API.
// Reduce focus marker latitude by small amount to ensure it is always on top of the
// corresponding stop marker (i.e., so its not identical to stop marker latitude)
LatLng latLng = new LatLng(stop.getLatitude() - 0.000001, stop.getLongitude());
Marker mCurrentFocusMarker = mMap.addMarker(new MarkerOptions().position(latLng));
When you slightly reducing the latitude of the marker you want on top, Google Maps will then render this marker on top of other marker.
But, it would be nice to have official z-order rending control via an API.
ch...@appspot.gserviceaccount.com
Automatic regression verification started for measurement:
ChromiumPerf/win-10_laptop_low_end-perf/v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_sum/browse_social/browse_social_twitter_2018
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/9bd3397d-c0f1-4e62-9a3e-4e2601b43123
ChromiumPerf/win-10_laptop_low_end-perf/v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_sum/browse_social/browse_social_twitter_2018
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/9bd3397d-c0f1-4e62-9a3e-4e2601b43123
pe...@google.com
ch...@appspot.gserviceaccount.com
📍 Pinpoint job created and queued.
https://pinpoint-dot-chromeperf.appspot.com/job/15dd69a6610000
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: v8.browsing_desktop
Story: browse:social:twitter:2018
Measurement: v8:gc:cycle:main_thread:full:incremental:mark:cpp
The job has been scheduled on the "win-10_laptop_low_end-perf" queue which currently has
1 pending jobs.
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: v8.browsing_desktop
Story: browse:social:twitter:2018
Measurement: v8:gc:cycle:main_thread:full:incremental:mark:cpp
The job has been scheduled on the "win-10_laptop_low_end-perf" queue which currently has
1 pending jobs.
ch...@appspot.gserviceaccount.com
Automatic bisection started for measurement:
ChromiumPerf/win-10_laptop_low_end-perf/v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_sum/browse_social/browse_social_twitter_2018
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ChromiumPerf/win-10_laptop_low_end-perf/v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_sum/browse_social/browse_social_twitter_2018
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ch...@appspot.gserviceaccount.com
<b>📍 Found a significant difference at 1 commit.</b>
14 revisions compared.
https://pinpoint-dot-chromeperf.appspot.com/job/15dd69a6610000
<b>Reland "[heap,cppgc] Unified heap incremental marking schedule"</b> by mlippautz@chromium.org
https://chromium.googlesource.com/v8/v8/+/68b1dbfedeba474e008703c613c3c2169d71cca4
v8:gc:cycle:main_thread:full:incremental:mark:cpp: 47.42 → 79.88 (+32.46) (+68.45%)
Understanding performance regressions:
http://g.co/ChromePerformanceRegressions
Benchmark documentation link:
https://bit.ly/system-health-v8-benchmarks
You can view the full results and re-run the Pinpoint job at:
https://pinpoint-dot-chromeperf.appspot.com/job/15dd69a6610000
If you think Pinpoint blamed the wrong commit, please add issue to
`Chromeperf-CulpritDetection-NeedsAttention` (hotlist:5670048) and
unassign yourself so that a sheriff can help diagnose.
14 revisions compared.
<b>Reland "[heap,cppgc] Unified heap incremental marking schedule"</b> by mlippautz@chromium.org
v8:gc:cycle:main_thread:full:incremental:mark:cpp: 47.42 → 79.88 (+32.46) (+68.45%)
Understanding performance regressions:
Benchmark documentation link:
You can view the full results and re-run the Pinpoint job at:
If you think Pinpoint blamed the wrong commit, please add issue to
`Chromeperf-CulpritDetection-NeedsAttention` (hotlist:5670048) and
unassign yourself so that a sheriff can help diagnose.
Description
Internal (Googlers-only) Reports:
- Chromium:
(Legacy) Chromeperf Report:
Top 1 regressions (out of 1, with 0 improvements) in this group:
- ChromiumPerf/mac-intel-perf/v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_avg/browse_tools/browse_tools_docs_scrolling
80.77%: 0.9205000000000001 -> 1.6640000000000001 ms
Top 1 affected measurements in mac-intel-perf:
- v8.browsing_desktop/v8:gc:cycle:main_thread:full:incremental:mark:cpp_avg/browse_tools/browse_tools_docs_scrolling
80.77%: 0.9205000000000001 -> 1.6640000000000001 ms
Regressions grouped by v8.browsing_desktop includes data from the following benchmarks with listed owners:
v8.browsing_desktop: almuthanna@chromium.org, cbruni@chromium.org, vahl@chromium.org
Commits in this range:
Chromium Git Hash:
Chromium Commit Position:
V8 Commit Position:
WebRTC Git Hash: