Skip to content

Issues: webspecs/url

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

30 Open 8 Closed
30 Open 8 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

rdflib.js has a URI parser and relativizer
#44 opened Jan 7, 2015 by timbl
2
Old python URI parser from SWAP
#43 opened Jan 7, 2015 by timbl
Import Node.js tests
#42 opened Jan 7, 2015 by domenic
1
Add a "relativizer" function to the API
#41 opened Jan 7, 2015 by domenic
Cannot find module 'pegjs'
#40 opened Jan 4, 2015 by duerst
5
Add method to return delegation boundary of a URL
#39 opened Dec 30, 2014 by hillbrad
make explicit proposal about moving URL-LS into IETF IETF
#38 opened Dec 28, 2014 by masinter
2
be explicit about change control issue IETF
#37 opened Dec 28, 2014 by masinter
point to W3C bugzilla as evidence of past WHATWG/W3C work IETF
#36 opened Dec 28, 2014 by masinter
list more radical rewrite as a possible outcome IETF
#35 opened Dec 28, 2014 by masinter
clarify "scheme specific definitions" problem IETF
#34 opened Dec 28, 2014 by masinter
note kinds of interop issues IETF
#33 opened Dec 28, 2014 by masinter
clarify "parameterization" problem IETF
#32 opened Dec 28, 2014 by masinter
are naming in APIs a problem IETF should solve IETF
#31 opened Dec 28, 2014 by masinter
IETF examples of using "URL" rather than "URI" IETF
#30 opened Dec 28, 2014 by masinter
be clearer about problem-statement draft purpose, and plan of work IETF
#29 opened Dec 28, 2014 by masinter
note possibility of implementation-dependent file: IETF
#28 opened Dec 28, 2014 by masinter
any update to 3986 must meet requirements for updating IETF Standard IETF
#27 opened Dec 28, 2014 by masinter
test URL-encoding of forms in HTML
#25 opened Dec 26, 2014 by masinter
RFC 3987 topics not included in the URL standard IETF
#18 opened Dec 17, 2014 by masinter
1
domainToUnicode cannot be defined in terms of domainToASCII WHATWG
#16 opened Dec 9, 2014 by annevk
3
What does invoke mean? WHATWG
#15 opened Dec 9, 2014 by annevk
2
"full stop code points" WHATWG
#13 opened Dec 9, 2014 by annevk
7
Writing IPv4 addresses WHATWG
#12 opened Dec 9, 2014 by annevk
4
ASCII whitespace is no longer defined WHATWG
#11 opened Dec 9, 2014 by annevk
2
ProTip! Find all open issues with in progress development work with linked:pr.