The Wayback Machine - https://web.archive.org/web/20200612025324/https://github.com/topics/dash
Skip to content
#

dash

Here are 803 public repositories matching this topic...

dash
KIMwofe
KIMwofe commented Mar 17, 2020

中文用户请注意:请尽量用英文描述你的 issue,这样能够让尽可能多的人帮到你。

If you want to report a bug, please provide the following information:

ranst91
ranst91 commented Jun 10, 2018

Browser: Chrome (latest)

OS: Windows 10

Clappr Version: 0.2.95

Going through all issues related to logging, it seems like someone insisted on having fatal errors logged without an open to turn them off.

I'd appreciate providing of any way to disable also fatal errors, as it makes no sense to have them on production.

Also, the documentation (API reference) does not supply

joeyparrish
joeyparrish commented May 1, 2020

In many older tutorials, we use things like var and .then() that we forbid in our actual codebase. It would be more readable if the docs used a more modern syntax, especially around Promises. Not only is await easier to read, but our use of .then() in docs may mislead a reader into thinking that they must do the same.

flavioribeiro
flavioribeiro commented Sep 23, 2019

According to the HLS specification, we must sinalize that a given audio track is DVS by the addition of CHARACTERISTICS="public.accessibility.describes-video" tag. I wonder if we should implement an option at the Sequence level on mapped mode where I set "dvs": true or something and that propagates all the way to the HLS manifest. Thoughts on this one @erankor?

More information about this o

Barahten
Barahten commented Apr 20, 2020

Apparently the parsing process has some kind of error, if a sprite is specified in the VTT file relative to the VTT file, then the player loads the sprite relative to the root of the site
2020-04-20-205114
2020-04-20-205250

In the case that is

0mp
0mp commented Jan 28, 2019

I'm packaging modernish for FreeBSD now. Usually, we put examples under share/examples/name, documentation under share/doc/name and any other data, that do not belong to any of the aforementioned directories, into share/name.

I wonder if you'd like to follow the same convention in this repository.

The reason is that I am not sure if I should move modernish examples to a standard pla

tko
tko commented Jun 13, 2015

When you install docsets that have underscores in the name the end result is rather unpredictable, e.g.

  • Bootstrap_2 => Bootstrap.docset
  • Bootstrap_3 => Bootstrap 3.docset
  • Common_Lisp => Common Lisp.docset
  • Emacs_Lisp => Emacs Lisp.docset

In a way none of docsets are available after installation due to underscore / whitespace mismatch, not to mention the loss of '2' even. I

Improve this page

Add a description, image, and links to the dash topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the dash topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.