-
Updated
Feb 19, 2020 - JavaScript
web-development
Here are 1,328 public repositories matching this topic...
-
Updated
Feb 19, 2020
-
Updated
Feb 19, 2020
-
Updated
Feb 19, 2020
DNS preanalyze
First of, thanks a lot for this very nice project :)
Documentation?
I have been playing quite a bit with rocket and have enjoyed all the very detailed examples listed here.
It appears though that they are not all following rustfmt convention.
I though it will be nice to apply formatting on those.
Thanks a lot !
-
Updated
Feb 18, 2020 - JavaScript
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
The crate actix_rt is already a dependency and thus should be available for use.
use actix_web::{get, web, App, HttpServer, Responder};
#[get("/{id}/{name}/index.html")]
async fn index(info: web::Path<(u32, String)>) -> impl Responder {
format!("Hello {}! id:{}", info.1, info.0)
}
#[actix_rt::main]
async fn main() -> std::io::Result<()> {
HttpServer::new(|| App::new().
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
Feb 19, 2020
-
Updated
Feb 18, 2020 - JavaScript
It seems that Shiny chooses random ports from 3000-8000 for connections. Some possible improvements that would be desirable:
- document that this is the random port range
- allow specifying a different random port range
- some mechanism for determining if the port is available before it is selected?
- a way to exclude ports from the range
The context here is RStudio Server and users who w
-
Updated
Feb 19, 2020
-
Updated
Feb 17, 2020
-
Updated
Feb 19, 2020 - C
-
Updated
Feb 19, 2020 - JavaScript
-
Updated
Feb 16, 2020 - CSS
Mainly due to defaulting of .any.js and not inserting the necessary boilerplate.
-
Updated
Feb 19, 2020 - Swift
-
Updated
Feb 18, 2020
-
Updated
Feb 19, 2020 - JavaScript
-
Browser and version:
Chrome 6x -
Version of Leaflet (
L.version):
1.3.0 -
Version of esri Leaflet (
L.esri.VERSION):
2.1.4
Steps to reproduce the error:
Can be seen in the jsbin below. Using leaflet 1.1 there's no error but still no layer is visible.
- Use leaflet 1.3.0
- Try adding the following layer as dynamicMapLayer https://ags.moin.gov.il/arcgis/rest/services/Planning
-
Updated
Feb 16, 2020 - JavaScript
-
Updated
Feb 9, 2020 - Python
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.
"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
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."
In HTML section there is a question:
And the answer is from MDN's HTML5 docs:
https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/HTML5
Probably something different is meant in the original question. I understand it as a question about tec