A user landing on the page can be confused right now, believing they can type immediately. However, the app does not begin with any active note, nor does it have an example note.

In the case that no notes exist on initial load, create a new empty note. Do not create a new empty note if they delete all notes - only initial load.

Memory management in the documentation is illustrated by an example which shows a case where no manual memory management is necessary. The other is an example of an array, which is freed by a free method.

There is no other information on how the programmer can differentiate between cases where manual memory management is necessary and where it isn't, other than that leaks will be reported at ru

mapbox-gl-js version: 1.3.1

browser: *

Why scale control uses different earth radius than mercator projection code? Is this ok?

https://github.com/mapbox/mapbox-gl-js/blob/2020f3f9ced516086508925411bd098fbb4c3234/src/ui/control/scale_control.js#L130

https://github.com/mapbox/mapbox-gl-js/blob/2020f3f9ced516086508925411bd098fbb4c3234/src/geo/mercator_coordinate.js#L9

It seems that the official Javadoc is not up to date. I found differences in the latest releases and Javadoc site -> https://developers.google.com/protocol-buffers/docs/reference/java/.

I checked for UnsafeByteOperation.java at Javadoc site and at [github repo](https://github.com/pr

提交 Issues 请提供

1. 提供发生错误的步骤，最好有 GIf 动图
2. 异常日志（尽量详细，异常日志可以使用MD语法）

对于没有提供详细日志的 Issues 将直接关闭。谢谢

• It would be great to update the README to mention the additional utilities that are now supported by the SDK.
• Improve the content of the README by removing replicated information and providing URL's of the appropriate document.

Current behavior:

On every run, cypress will clean it's screenshots folder (as mentioned in the documentation). Unfortunately on Windows it is likely that the filenames are too long and thus can not be deleted. When cypress tries to do this, it ignores those files.
We take all screenshots after the test runs and publish them as build artifacts. So this is a problem as we always see old sc

Description

So our function arrayToHtmlList is in a pretty bad space and could use an update. We already had some discussion over at #675 but I wanted to move the update discussion over to an issue for more visibility.

Current problem:

It uses an awkward query selector instead of the `document.prototype.getElementBy

As requested in #2626, we should document all the fields available via the context as they are not really discoverable. The doc should include grpc functions like SetHeader/Method/etc as well as fields stored directly within the context like metadata and peer info.