Godot: draw_line and Sprite3D don't work in HTML5

[bozydar]

Operating system or device - Godot version:
Fedora 23, x86_64, Godot Engine v2.1.stable.official

Issue description (what happened, and what was expected):
Using draw_line on a TextureButton works improperly when exported to HTML5.

Steps to reproduce:
Drawing on TextureButton with a script.

func _draw():
    draw_line(Vector2(3, 3), Vector2(47, 47), Color(0.5, 0, 0, 0.6), 30)
    draw_line(Vector2(3, 47), Vector2(47, 3), Color(0.5, 0, 0, 0.6), 30)

Running the application (good):

Running the application in Firefox 50.0 after exporting it to HTML5 (bad)

Note: There is no problem with drawing with draw_primitive() function.

Link to minimal example project (optional but very welcome):

[kubecz3k]

Conversation have been cleaned and locked because of massive offtopic discussion regarding https://github.com/godotengine/godot/issues/6965 and https://github.com/godotengine/godot/issues/4261

[akien-mga]

Unlocking the issue as it's still valid and should be available for on-topic comments. Sorry @bozydar for the mess (pun intended) that happened here.

Note: Any further off-topic discussion may be deleted without notice.

[leonkrause]

draw_line uses _draw_primitive in the OpenGL ES 2 rasterizer. That function is missing an alternative implementation for WebGL which doesn't use client side arrays (web platform defines GLES_NO_CLIENT_ARRAYS for that purpose), causing this error, independent of line width.

Sprite3D suffers from the same problem (#6147)

Not looking further into this myself with the ES3 rasterizer in the works

[bojidar-bg]

Is this still valid on master/3.0 (as I heard we now have a ewb platform sort-of working)?

[leonkrause]

Tested this, fixed in 3.0

[ghost]

First of all thank you for your report and sorry for the delay.

We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.

We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible and comment about it here?

For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.

Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.

Thanks in advance.

Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

[Zireael07]

Why is this still open? Eska said it's fixed in 3.0.

[ghost]

I'll close it then.

[HummusSamurai]

@eska014 Do you remember the commit that fixed this in 3.0 ? I'm using draw_line() in 2.1 and would like to try backporting it if it's possible.

[akien-mga]

The renderer was changed between 2.1 and 3.0, and likely fixed this issue. That can't be backported :)