Assigned
Status Update
Comments
ca...@google.com <ca...@google.com>
ca...@google.com <ca...@google.com> #2
> - low-quality 3GPP streams over RTSP (supported, but low-quality and patent encumbered)
YouTube also allows for low-quality MPEG-4 streams, but the problems are the same.
YouTube also allows for low-quality MPEG-4 streams, but the problems are the same.
js...@gmail.com <js...@gmail.com> #3
Can Totem be so hard for Google to support?
js...@gmail.com <js...@gmail.com> #4
Christian, there's no need to add this sort of comments to this bug.
Please, only add comments if you're one of the Totem developers, and let's wait for an answer from the YouTube developers.
Please, only add comments if you're one of the Totem developers, and let's wait for an answer from the YouTube developers.
ca...@google.com <ca...@google.com> #5
Maybe it would be easier for YouTube to provide "sponsor" data as part of the protocol? The application could then fetch the ad content and display it either along, during or before playing the video.
js...@gmail.com <js...@gmail.com> #6
[Comment deleted]
18...@gmail.com <18...@gmail.com> #7 Restricted+
Restricted+
Comment has been deleted.
18...@gmail.com <18...@gmail.com> #8 Restricted+
Restricted+
Comment has been deleted.
18...@gmail.com <18...@gmail.com> #9 Restricted+
Restricted+
Comment has been deleted.
js...@gmail.com <js...@gmail.com> #10
Come on you lousy bastards at google, let us use whatever apps we want.
18...@gmail.com <18...@gmail.com> #11
Folks, negative +1 comments won't help anything, and just email spams everyone who cares about this bug.
Show your support by starring the issue, and only leave a comment if you're a developer involved in the issue. Thanks!
Show your support by starring the issue, and only leave a comment if you're a developer involved in the issue. Thanks!
js...@gmail.com <js...@gmail.com> #12
Please stop spamming me with childish, insulting, or "me too!" comments just because I clicked the star here, otherwise I will have to remove my vote again. Thanks.
js...@gmail.com <js...@gmail.com> #13
Google, please let us live free! We love Totem.
js...@gmail.com <js...@gmail.com> #14
Having youtube videos in totem is a nice thing for the Linux community.
js...@gmail.com <js...@gmail.com> #15
Free the Web
ca...@google.com <ca...@google.com> #16
Free the YouTube
js...@gmail.com <js...@gmail.com> #17
Please stop posting useless comments.
This is a bug report, not a comment thread.
This is a bug report, not a comment thread.
js...@gmail.com <js...@gmail.com> #18
Google, I'm sorry, but your behaviour in this situation looks unreasonable.
Perhaps something is not told.
@cybolic, this is a bug, indeed, and comments here, are essentially "affects me too" confirmations.
Perhaps something is not told.
@cybolic, this is a bug, indeed, and comments here, are essentially "affects me too" confirmations.
pl...@gmail.com <pl...@gmail.com> #19
> comments here, are essentially "affects me too" confirmations.
That's what the stars are for. If you want to send Google a message, please use *their* e-mail address, not addresses of all the people who starred this. It's getting really annoying.
That's what the stars are for. If you want to send Google a message, please use *their* e-mail address, not addresses of all the people who starred this. It's getting really annoying.
js...@gmail.com <js...@gmail.com> #20
@_deepfire
Yes they are "affect me too" confirmations, however that is what the star is for at the top left of the page. "Me too" comments do nothing to help the bug get fixed.
Also, statement like "your behavior in this situation looks unreasonable" in itself seems unreasonable. Google is not just one person who's mind can be swayed by silly comments. It is a massive entity that takes time to make changes, especially ones that have legal ramifications.
This bug report is an indication we would like some change, and voting for it with the star lets Google know that this issue is one we feel is important to consider. Attempting to scold them will not make them move to it faster. A well reasoned, and rational discussion as to why we would like the features we would like is the most likely to succeed. I, and I'm sure others, would appreciate it if you, or anyone else, would limit your usage of the comment field to only relevant information to the actual bug.
Thanks in advance.
Yes they are "affect me too" confirmations, however that is what the star is for at the top left of the page. "Me too" comments do nothing to help the bug get fixed.
Also, statement like "your behavior in this situation looks unreasonable" in itself seems unreasonable. Google is not just one person who's mind can be swayed by silly comments. It is a massive entity that takes time to make changes, especially ones that have legal ramifications.
This bug report is an indication we would like some change, and voting for it with the star lets Google know that this issue is one we feel is important to consider. Attempting to scold them will not make them move to it faster. A well reasoned, and rational discussion as to why we would like the features we would like is the most likely to succeed. I, and I'm sure others, would appreciate it if you, or anyone else, would limit your usage of the comment field to only relevant information to the actual bug.
Thanks in advance.
pl...@gmail.com <pl...@gmail.com> #21
Please allow 3rd party players (Totem etc...) to use high quality video streams.
js...@gmail.com <js...@gmail.com> #22
DO NOT COMMENT ON THIS ISSUE!
By commenting, you are doing a disservice to the 1537 people who have starred this issue and therefore get an email every time someone comments. Unless you have something other than "omg, this needs to happen" to say, please stop posting.
Sorry everyone for the useless comment.
By commenting, you are doing a disservice to the 1537 people who have starred this issue and therefore get an email every time someone comments. Unless you have something other than "omg, this needs to happen" to say, please stop posting.
Sorry everyone for the useless comment.
ca...@google.com <ca...@google.com> #23
"- addition of a YouTube watermark and specific behaviour when clicked (like launching the video's page in a web browser)
- allowing direct access to Web-M streams, either through HTTP or RTSP"
These options are reasonable.
- allowing direct access to Web-M streams, either through HTTP or RTSP"
These options are reasonable.
js...@gmail.com <js...@gmail.com> #24
Im tired of all the kids spaming this thread, Im removing my star.
js...@gmail.com <js...@gmail.com> #25
Fuck you morons, I'll unstar this issue.
Retards !
Retards !
js...@gmail.com <js...@gmail.com> #26
Let totem live!
js...@gmail.com <js...@gmail.com> #27
[Comment deleted]
js...@gmail.com <js...@gmail.com> #28
I'm linux user. flash plugins have heavy resouce consuption. Why I can see with totem you tube videos in low quality and don't in high. It's this correct?
js...@gmail.com <js...@gmail.com> #29
Okay I don't know anything about these you too whatever videos of people in here 10 the green and some people that but I don't like me. Don't think I know you probably could be My family gonna be like 2 sisters they don't like me because ? I like to make a report. The people the ribbon hungry spec this is the 2011 . Tell me how 1 can do these. Thank you very much
Description
The issue is easily reproduced by attempting to add an outline (stroke) of any width under Landscape-Human-made(man_made)-Buildings. The expected changes do not show in the rendered map in the editor or when loading the map elsewhere.
I have attached a screenshot (3d-Issue.jpg) where I have the building outline (stroke) set to red and the stroke width set to 4 (building type is 3d), but the outline doesn't show when rendering the map. I have also attached a second screenshot (3d-Expected.jpg) using Photoshop to mock up an example of the expected behavior when adding the building outlines (stroke). These red building outlines in this second screenshot were added in Photoshop to show the expected behavior of the stroke and width feature, when editing buildings in the Map Styles editors.
The same issue also exists when the building type is set to footprint, where the building footprints are never outlined as expected. Similarly, I have attached a screenshot (Footprint-Issue.jpg) where I have the building outline (stroke) set to red and the stroke width set to 4 (building type is Footprint), but the outline doesn't show when rendering the map. I have also attached a second screenshot (Footprint-Expected.jpg) using Photoshop to mock up an example of the expected behavior when adding the building outlines (stroke).