When the frontend initially started on a RPi2 using iceweasel, it reported a memory usage of around 15%, after 5 days iceweasel showed a memory consumption of around 41%. Killing iceweasel and restarting it, it came back up at around 15%. The screen contained a single feed with a single piece of htmltext content.

While I was trying to figure out a problem with chromium I noticed that the markup is all out of whack. I went back at looked at our production site with Chrome and it is the same...

multiple html, head, title, body and closing tags...

I need the content to refresh more often. It seems like there is about a 2 minute delay on new content getting to the frontend. Is there a setting that can be changed? In my case its an updated RSS feed, so its not a "new" piece of content just and updated version of it...

If there is a simple delay value set in the code somewhere that I can modify on my setup can someone point me to it, I've been looking but cant find it.

How do I execute the concerto-frontend tests? There appears to be some test fixtures in this repository, but I haven't had the foggiest idea on how to run them.

The canonical BBC RSS feed still looks a bit odd -- still like one big paragraph. This isn't particularly unique to the new frontend -- the sizing spacing of dynamic content here has long been an issue.

https://www.polymer-project.org/1.0/

At the current state of master, the time field blinks somewhat randomly in Firefox 52.2.1 ESR.

• Expected behavior: Every 15 seconds, the current time is re-evaluated and the contents of the time field are seamlessly replaced.
• Observed behavior: Every 15 seconds, the contents of the time field disappear entirely, only to reappear at a later time. Sometimes it reappears a mere fraction of a second later, but it usually takes several seconds, and sometimes does not reappear within any given 15-second period. The accuracy of the time, when it is displayed, does not appear to be affected.

Other text fields do not appear to exhibit the same blinking behavior, even when they only contain one item. Checking the console, there do not appear to be any content updates coming through for the time field.

In my testing, I have observed that this behavior does not occur in Firefox 45.3.0 ESR, Firefox 48.0, or Chrome 58.0.3029.110. This came up in testing a new upgrade from Concerto 2.3.1, so perhaps some settings have changed that I am missing?

It would be useful to have a text content area, so that as new RSS items become available they are appended to the bottom. This would be helpful in situations where feeds report driving conditions or accidents are reported as they occur. As opposed to cycling through the RSS content you would simply see the most recent at the bottom. Maybe have a transition that highlights the new entry for a couple minutes.

Hi,
is it possible that you change the moment.min.js to moment-with-locals.min.js and add a new property to the screen settings like timezone (best) or the field_properties like time_format.
And pls dont use moment direct, make a instance an set the locale there, so it would be possible to have different screens with different locales.

At the moment we are not able to show german day or month names.

kind regards

Ability to run screens using cached content, while internet connection is down. It also aides to minimize transfer if clients are using a transfer-capped internet connection like mobile internet connection (3G/UMTS etc)

The frontend does not appear to work when Concerto is deployed somewhere other than the root path of the domain.

Setup: concerto is deployed to a sub-URI, as https://example.com/concerto. I'm using concerto_frontend-0.2.0.

Symptoms:

• Black Screen
• Developer tools show a 404 on https://example.com/frontend/4/setup.json, (when it should have requested https://example.com/concerto/frontend/4/setup.json, as the actual frontend is accessed at http://dev.mikldt.net/concerto/frontend/4)

The cause seems to be that URLs in the app are generated with a leading / and appended to a baseUrl variable. baseUrl is set to an empty string in concerto-screen.html, line 70. When I changed this to my sub-URL ("/concerto") by hacking the generated assets, setup.json was loaded successfully.

It would be ideal if the correct URL could be auto-detected in js (since the javascript should know the current URL) or included in the _frontend.html to be passed to the javascript. Alternately, it could go in a config somewhere. Unfortunately I don't think I have the polymer expertise to pull this off myself right now.

@augustf noticed this one. The issue was narrowed down to the Rails 4.2 migration in core Concerto and appears to be caused by the screen's frontend cache key changing constantly (messages in the console). It might be worth looking into any changes that could have broken the screen's frontend caching method, since the issue no longer occurs when rolling back before the Rails 4.2 branch merge.

As mentioned in concerto/concerto#1184, we want the cursor to be set off in CSS when the frontend is running on a computer, but visible in preview mode.

Field config support needs to be implemented for features like transitions, scrolling ticker text, and anything else that the original frontend used to allow.

Per concerto/concerto#550, content should not be re-loaded when it comes after itself in sequence.

Support field config parameter here concerto/concerto#1305

Uncaught TypeError: Cannot read property 'j' of undefined
frontend.js:64

Windows 7 Pro
24G ram
Xeon processors
Chrome 43.0.2357.134
This happens during the preview while setting up the UI for use.

Content sizes for both images (scroll bar still appears) and text (font-size) are not adjusted to fit the screen's fields properly.

Concerto Version: 2.3.0.
ConcertoFrontend via rubygems Gem version: 0.0.8

http://mysite/frontend/1

Google Chrome 45.0.2454.85 m - OK

FireFox 40.0.3 (webobjects is enabled) - Black Screen
in console 1 warn and 1 error
mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create 1:215:0
TypeError: this.$ is undefined 1:8948:8

IE11 - Black Screen

Add support for scrolling ticker text animation via field configs. Like a CNN scrolling text marquee at the bottom. There are already animations for sliding content in and out, but this request is for a continually scrolling stream of content.

The screen did not reload when a field config was changed, a field' style was changed, a new field was added, nor when the background image was changed. We generate a header which indicates when anything screen/template/field/position changes and send it with each piece of content:

https://github.com/concerto/concerto/blob/master/app/controllers/frontend/contents_controller.rb#L47

But the new frontend isn't looking at it. This same indicator is sent (I believe) as the etag when the setup.json is sent.

What do you think about changing the frontend from polling the setup.json every 8 seconds, to just checking that header each time it gets a piece of content?

Concerto Prelude was an initial attempt a while back to build a HTML5 application that would serve as a container for the Concerto Frontend for any HTML5-based application platform with the initial intent of being used for Google Chrome/Chrome OS based-kiosks and expanded to Chromecast while the SDK was available.

Prelude's build toolchain predates the acceptance of Node.js, Grunt, Bower, and Polymer in this space. This issue tracks the progress in deprecating the Prelude repository in favor of building a single frontend that can be packaged for the following platforms:

• Gem for Concerto Rails application
• Chrome App
• Google Cast - deploy to CDN for consumption by Chromecasts

Separately, Concerto Sonnet (a sender app framework for second screen devices - initially targeting Google Cast) will eventually exist to talk to Prelude.

Two people posted a similar problem on the forum:

I installed version 2.3.2 yesterday (completely fresh install, not an upgrade) and even with the timezone properly set the time is off by 5 hours (I need it to be eastern std time - and 5 hours is the difference - I think, so it seems to me that it is not taking into account the local time zone setting).

Currently the template is only loaded when the screen is first created. We should check periodically to see if it needs to be changed or the fields need to be adjusted.

Per #53

I created a new field and made it type "Text". I added content to it but the screen never updates it. I think the problem is related to the web browser caching the content for the feed. I went into another tab and went to the url http://server/frontend/[screen]/fields/[fieldid]/contents.json and it displayed outdated data... I performed a regular refresh (F5) and it remained the same. I performed a SHIFT+F5 and it refreshed the content and the tab running my screen eventually refreshed the field with the new content.

Just want to add - maybe this is the reason, not really sure on the logistics of browser caching -- my content is not changing much at the moment. The only thing that's actually changing is a timestamp within the content which just shows when the last time the RSS feed data was pulled. Could it be seeing the same exact number of bytes and thinking there was no change in content?

We should change the time/date field as unobtrusively as possible.

In #3, it was mentioned that RegisterContentTypes() uses the content element's name attribute instead of the constructor attribute to build keys for the Types object. A reference to the element is then saved as the value by using the constructor name and window object.

It was mentioned this needed to be improved. Maybe the element's constructor attribute should be used as the key instead?

Polymer and its supporting Web Components are esssentially Chrome-proprietary right now. As in #19, WC support can be turned on in Firefox, but is considered highly experimental. Since the Concerto Player uses Chromium, that won't be a problem for our builds, but current users on alternative platforms updating to a future 2.3 release will need to be mindful -- particularly Raspberry Pi users in Midori.

This was helpful to me in following support for Web Components: http://jonrimmer.github.io/are-we-componentized-yet/

While I don't believe there's anything for us to do on this currently (having two parallel frontends sounds a bit crazy), I'll leave this issue here to track the fact that we're effectively Chrome-only for the time being.

Investigating an issue where the frontend presents a black screen on Firefox. @augustf pointed this out after testing the latest Concerto build. The frontend does work on Chrome at the moment.

After concatenating all of the frontend files, content types are unable to register properly. Each content calls the inherited registerContentType() function, but querySelector('polymer-element') cannot find the correct element and causes the elem variable to be undefined.

The new frontend should support time formatting and the ticker text marquee as explained here: https://github.com/concerto/concerto/wiki/Field-Configuration

May be related to #68 and concerto/concerto#1361

Since that issue was fixed now the screen only shows the first piece of content for each field on the screen. The error seen in the developer console is: Uncaught TypeError: Failed to execute 'animate' on 'Element': 'function (a){return a}' is not a valid value for easing(…)

We should have a build step which minifies / vulcanizes the frontend into one or two includes.

TypeError: this.Ec is undefined
frontend.js:64:298

Windows 7 Pro
24G ram
Xeon
Firefox 39.0
This happens on page load / reload randomly.

I use unclutter in my signsage devices to hide the cursor, but sometimes the alt text stills shows up on the screen. See the image linked below. Is there any way to disable the hover/alt text for the images from showing up?

https://ibb.co/mYy5FA

You're probably already aware of this...

From: concerto/concerto#289

We should implement hooks in the frontend to go back/pause/forward in the content being displayed

As mentioned in concerto/concerto#1095 , there needs to be documentation for the Frontend JS code. This is useful for those who want to embed it or create a screen independently of the Concerto frontend page.

This has been reported here: concerto/concerto#1361

The later versions of FF appear to not handle the 'replace' animation correctly as Chrome does. See https://github.com/concerto/concerto/issues/1451. Regardless, the neon-animation is deprecated https://www.webcomponents.org/element/PolymerElements/neon-animation.