silthus / chrome-enterprise-tab-rotate Goto Github PK

This appears to be no longer available at the Chrome webstore here: https://chrome.google.com/webstore/detail/enterprise-tab-rotate/phdmnkgnjkbnpmeaodonildfklccgimp

Can it be reinstated?

Describe the bug
Loading of externally hosted config fails, e.g. from Azure Edge.

To Reproduce
Steps to reproduce the behavior:

1. Upload the sample config to azure edge.
2. Configure the extension to use the config from azure.
3. Config will not load.

Expected behavior
The config should always load, regardless of the hosting location.

This issue provides visibility into Renovate updates and their statuses. Learn more

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency typescript to v4.7.2
• chore(deps): update dependency copy-webpack-plugin to v11
• chore(deps): update dependency eslint-plugin-jest to v26
• chore(deps): update dependency eslint-plugin-promise to v6
• chore(deps): update dependency ts-loader to v9
• chore(deps): update dependency webpack to v5
• chore(deps): update dependency webpack-cli to v4
• chore(deps): update github/codeql-action action to v2
• chore(deps): update jest monorepo to v28 (major) (@types/jest, jest, ts-jest)
• chore(deps): update semantic-release monorepo (major) (@semantic-release/changelog, @semantic-release/git, semantic-release)
• chore(deps): update typescript-eslint monorepo to v5 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• fix(deps): update dependency rxjs to v7

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): pin dependencies (@semantic-release/changelog, @semantic-release/git, @types/deep-equal, @types/jest, @types/jquery, @types/sinon-chrome, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, copy-webpack-plugin, coveralls, eslint, eslint-config-standard, eslint-plugin-import, eslint-plugin-jest, eslint-plugin-node, eslint-plugin-promise, eslint-plugin-standard, jest, jest-webextension-mock, rimraf, semantic-release, semantic-release-chrome, sinon-chrome, ts-jest, ts-loader, typescript, webpack, webpack-cli, webpack-extension-reloader, webpack-merge)
• chore(deps): update dependency @types/chrome to v0.0.188
• chore(deps): update dependency @types/google.analytics to v0.0.42
• chore(deps): update yarn to v3.2.1
• chore(deps): update dependency webpack-merge to v5.8.0
• chore(deps): update actions/checkout action to v3
• chore(deps): update actions/setup-node action to v3
• chore(deps): update actions/upload-artifact action to v3
• chore(deps): update dependency eslint to v8
• chore(deps): update dependency eslint-config-standard to v17

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Is your feature request related to a problem? Please describe.
Some websites do not display correctly on some screens. This is due to an invalid zoom level.

Describe the solution you'd like
I would like to be able to the define the zoom level per configured url.

Describe alternatives you've considered
As a workaround a separate extension can be used.

Additional context

The config could look like this:

{
	"websites": [{
		"url": "https://github.com/Silthus/chrome-enterprise-tab-rotate",
		"zoom": 0.5
	}]
}

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Application error (6): phdmnkgnjkbnpmeaodonildfklccgimp pending review so can't be edited

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-chrome plugin to add more helpful information.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Describe the bug
Extension disabled: "This extension violates the Chrome Web Store policy."

Screenshots

Desktop (please complete the following information):

• Microsoft Edge Version 101.0.1210.32 (Official build) (x86_64)
• Enterprise Tab Rotate 1.1.2

Additional context
The plugin doesn't appear to be available anymore, but enabling it remediates the issue.
But for how long?

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Chrome Web Store system error, please try again later.

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-chrome plugin to add more helpful information.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The add-on “Enterprise Tab Rotate” is generating a error message when downloading. The add-on worked fine before today.

v1.0.0

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://[secure]@github.com/Silthus/chrome-enterprise-tab-rotate.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀

Describe the bug
tabReloadIntervalSeconds is not working/unpredictable.

To Reproduce
Steps to reproduce the behavior:

1. Run this JSON: tinyurl.com/etb-test
2. Chrome opens 3 tabs and loads them.
3. On the first round every tab will reload when made active.
4. On the second round only the first tab will reload.
5. No tabs ever reload again.
   This behavious seems to change with different values of tabReloadIntervalSeconds.
   At one point every tab would reload every time is was made active.

Expected behavior
Tabs reload according to each tabReloadIntervalSeconds value.

Desktop (please complete the following information):

• OS: Macos Big Sur
• Browser: Chrome 88 64b

Additional context
I have a feeling this bug is what is affecting #37 .
I spent hours last October trying to find out why the tabReloadIntervalSeconds stopped working with multiple Chrome profiles/instances. Perhaps tabReloadIntervalSeconds was just buggy from the start, and multiple profiles was not hte issue?

Thanks for your time and continued efforts on this project, Silthus :)

We're using your addon to cycle through dashboards in the office, and it's awesome!

Configuration is user friendly and can be done remotely by anyone from our internal project management system, which webhooks to integromat.com, which produces a JSON file and uploads to ftp, which is fetched by Chrome Enterprise Tab Rotate (CETR) every XX secs. :)

We've had issues where the updated JSON file does not trigger an update in CETR.
Loading the JSON file in a browser confirms that the file is updated.
When looking in CETR settings we noticed that the options were not saved - or perhaps they are not loaded when opening Options a second time? Here's a short screen recording: http://somup.com/cYQUFLljU1

We can't be sure if the Options are not saved, which prevents loading the updated JSON file, or there's a bug with fetching the JSON file, but would be happy to help get rid of the bug in any way we can.

/f

In addition, when the rotation plug-in is running, and we change the policy values, these aren't picked up by the running plug-in until you hit the "save" button. (starting and stopping will keep running on the last "saved" config)

Originally posted by @CorCornelisse in #1 (comment)

Currently only remote JSON configs are supported. To make full use of the extension it would be useful to configure the complete tab rotation with a local config and provide it via policy.

In the settings GUI the config must be provided in a separate tab as JSON. In the policy it can be configured with separate keys.

The schema would look like this:

{
    "type": "object",
    "properties": {
        "source": {
            "type": "string",
            "title": "Config type.",
            "description": "DIRECT (default) or URL. You can load a config from a URL or use the direct_config section for a direct config."
        },
        "url": {
      "type": "string",
      "title": "Config url.",
      "description": "Provide the url to load your tab rotate config."
    },
    "retry_count": {
        "type": "integer",
        "title": "Retry count (default: 5)",
        "description": "How often should the extension try to load the config until it gives up. -1 for infinite."
    },
    "retry_interval": {
        "type": "integer",
        "title": "Retry interval in seconds (default: 60s)",
        "description": "How long should the extension wait to retry loading the config after an error occured."
    },
    "reload_interval": {
        "type": "integer",
        "title": "Reload interval in seconds (default: 60s)",
        "description": "How often should we reload the config and check if there were any changes."
    },
        "config": {
            "type": "object",
            "title": "Direct config.",
            "description": "You can specify a direct config that is loaded by the plugin. You need to set ConfigType to DIRECT.",
            "properties": {
                "autoStart": {
                    "title": "Autostart tab rotation.",
                    "description": "If set to true the plugin will automatically start rotating the configured tabs when chrome starts.",
                    "type": "boolean"
                },
                "lazyLoadTabs": {
                    "title": "Lazy load tabs.",
                    "description": "If set to true will only load two tabs and the rest async in the background.",
                    "type": "boolean"
                },
                "fullscreen": {
                    "title": "Fullscreen mode.",
                    "description": "If set to true will enter fullscreen after starting.",
                    "type": "boolean"
                },
                "websites": {
                    "type": "array",
                    "id": "ListOfWebsites",
                    "items": {
                        "type": "object",
                        "properties": {
                            "url": {
                                "type": "string"
                            },
                            "duration": {
                                "type": "integer"
                            },
                            "tabReloadIntervalSeconds": {
                                "type": "integer"
                            }
                        }
                    }
                }
            }
        }
    }
} 

//cc @CorCornelisse
//migrated from KevinSheedy/chrome-tab-rotate#44

Describe the bug

Running on Google Chrome. :

I have a little concern, when I use it on 2 instances (one screen portrait mode and the other is landscape).
So I have 2 jason config file. I start the first rotator under my user profile and
the second under another user profile (using RunAs).

Both are running and rotating for 10 minutes and they stop rotating.
If I clause one of chrome process, the second one can be restarted and work well. I've try different duration and tab refresgh parameter in the json config without succes.

It's like timer get confuse event if the running une 2 set of credential.

Could you try this configuration and try to figure out ? I can give you the URL of my 2 json config.

Alone : both of my json config work well. as soon as second instance running, It just stop rotating after some minutes

According to the documentation setting lazyLoadTabs to true will "Open empty tabs and load the website on the first rotation", so i figure setting it to false will "Open all tabs and load websites immediately"

When i run http://weboost.dk/tabcycle.json there is no difference. It always lazy loads.

Chrome v85.0.4183.121 (Official Build) (64-bit)
Enterprise Tab Rotate v1.1.1

Happy to help in any way.

/frm

• configuration documentation
• policy documentation
  • ChromeOS
  • Local
  • Remote
  • Registry
  • GPO
• end user documentation
• contributing documentation