-
Updated
Apr 2, 2020 - JavaScript
web-development
Here are 1,373 public repositories matching this topic...
-
Updated
Apr 3, 2020
When a property is accessed on an object and if the property is not found on that object, the JavaScript engine should looks at the object's __proto__(different browser has their own implement) .Or, looks at the prototype of its constructor.
-
Updated
Mar 28, 2020
DNS preanalyze
DNS preanalyze is a way to reduce DNS analyze time:
<meta http-equiv="x-dns-prefetch-control" content="on" />
<link rel="dns-prefetch" href="http://www.baidu.com" />
Feature Request
It just took me about half an hour to find out how to define a custom 404 handler. I was trying to get a #[get("/<path..>")] route to work for that, and the only reason it didn't work is because I also had another, high-priority catch-all NamedFile route. Finally, I found out through this issue that I could just write
-
Updated
Nov 19, 2018 - JavaScript
The feature list on the documentation is wrong. It refers to a missing feature. See at:
https://github.com/actix/actix-web/blob/206733188478f4d18df376a72fac3a4938b99bd6/src/lib.rs#L79
I found that when looking for a way to disable to client build.
Correct the terminology used in code and documentation so that it is consistent with HTTPie and web standards. Examples:
- body parameter -> data field
- operator -> separator
I see the "Welcome" doc page mentions "component system", but it is very vague. Can you describe what are all the reasons that I'd want to use Whitestorm over plain Three.js, f.e. what are all the things I get that Three.js does no offer, so that I can better understand?
Thanks!
-
Updated
Mar 23, 2020
-
Updated
Jul 30, 2019 - JavaScript
hi,
the documentation of shiny::Progress says
initialize(session, min = 0, max = 1)
Creates a new progress panel (but does not display it).
Nevertheless it seems as if already the simple creation of a progress object (p<- Progress$new()) shows the Notification "message" without calling p$set(...) first.
here a very minimal example showing an undesired "message" notification.
``
-
Updated
Oct 25, 2018
-
Updated
Oct 7, 2019
-
Updated
Mar 25, 2020 - C
-
Updated
Apr 2, 2020 - JavaScript
-
Updated
Jan 21, 2020 - CSS
Mainly due to defaulting of .any.js and not inserting the necessary boilerplate.
-
Updated
Apr 1, 2020 - Swift
-
Updated
Jan 6, 2020
-
Updated
Apr 3, 2020 - JavaScript
- Browser and version:
All supported browsers;
- Version of Leaflet (
L.version):
1.6.0
- Version of esri Leaflet (
L.esri.VERSION):
2.3.3
Steps to reproduce the error:
- Add a
dynamicMapLayerto a leafletmapwith the following code:
this.mapServer = esri.dynamicMapLayer({
f: 'image',
url: URL_MAPSERVER,
transparent: true,
max
-
Updated
Mar 29, 2020 - JavaScript
-
Updated
Jan 21, 2020 - Python
"Attribute itemprop not allowed on element link at this point"
I get this errors for things like that:
<link rel=icon itemprop=logo href=ico.png>
<link rel=canonical itemprop=url href="https://example.org/">
Otherwise the spec says
"Every HTML element may have an itemprop attribute specified"
https://html.spec.whatwg.org/multipage/microdata.html#names:-the-itemprop-attribute
Goo
At the bottom of this page there is a link Read more about data sources but it goes no where. Upon inspection of the code I see that there are no docs for the backend yet.
Improve this page
Add a description, image, and links to the web-development topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the web-development topic, visit your repo's landing page and select "manage topics."
It's probably worth expanding on the script element.
At the very least I'd mention that
<script src="..."></script>blocks content rendering while the script loads and executes, and add a non-blocking example with<script async src="..."></script>.The scope of this project is not to explain every feature of each element that can go in
<head>, but for important features it's probably a goo