Nativescript 8.1 does not recognize <Tabs> - tabs

I could not understand how to use Tab component in Nativescript-vue after upadate Nativescript 8.1...
The below code was work collectly in Nativescript playground, however it got errors in my project.
Home.vue
<StackLayout row="1">
<Tabs>
<TabStrip>
<TabStripItem>
<Label text="Newest" />
</TabStripItem>
<TabStripItem>
<Label text="Daily" />
</TabStripItem>
<TabStripItem>
<Label text="Weekly" />
</TabStripItem>
<TabStripItem>
<Label text="Monthly" />
</TabStripItem>
</TabStrip>
<TabContentItem>
<Label text="NEWEST test" />
</TabContentItem>
<TabContentItem>
<Label text="DAILY test" />
</TabContentItem>
<TabContentItem>
<Label text="WEEKLY test" />
</TabContentItem>
<TabContentItem>
<Label text="MONTHLY test" />
</TabContentItem>
</Tabs>
</StackLayout>
My console
CONSOLE LOG: Loading inspector modules...
CONSOLE LOG: Finished loading inspector modules.
(UserNotifications) [com.apple.UserNotifications:Connections] [org.nativescript.firebasetest] Creating a user notification center
CONSOLE LOG: firebase.init done
NativeScript debugger has opened inspector socket on port 18183 for org.nativescript.firebasetest.
CONSOLE LOG: NativeScript-Vue has "Vue.config.silent" set to true, to see output logs set it to false.
CONSOLE LOG: TypeError: No known component for element Tabs.
***** Fatal JavaScript exception - application has been terminated. *****
NativeScript encountered a fatal error: Uncaught TypeError: Cannot read property 'setAttribute' of undefined
at
setStyleScope(file: app/webpack:/firebasetest/node_modules/nativescript-vue/dist/index.js:8550:0)
...
Reproducted minimum project package.json
"dependencies": {
"#nativescript/core": "~8.1.1",
"#nativescript/firebase": "^11.1.3",
"#nativescript/theme": "~3.0.1",
"nativescript-vue": "~2.9.0"
},
"devDependencies": {
"#nativescript/ios": "8.1.0",
"#nativescript/webpack": "~5.0.0",
"nativescript-dev-typescript": "^0.10.0",
"nativescript-vue-template-compiler": "~2.9.0"
}
I guess it's occour because of lack of any packages or plugins.
Is anyone know the environment for using Tabs in Nativescript-vue after Nativescript 8.1 update?

From the 8.0 release notes:
Important note about BottomNavigation and Tabs
BottomNavigation and Tabs ui components in core brought along Cocoapods whether your project used them or not. With 8.0, they now are provided by the community where they can receive more focused attention not bound or held up by NativeScript core updates.
is now available via #nativescript-community/ui-material-bottom-navigation
The api is the same however the component names can swap to what is found in the Readme.
is now available via #nativescript-community/ui-material-tabs
This is a drop in replacement.

Related

How to resolve a multipleLabellingTechniquesUsed error in a React app using ARC Toolkit

I was resolving accessibility issues using ARC toolkit. And I am stuck on one issue i.e.:
And here is my component markup:
{/* <label htmlFor="first-name-input">FirstName</label> */}
<input
aria-label={'First Name'}
aria-required="true"
autoComplete="off"
type="text"
placeholder="First Name"
name="first_name"
value={inputValue}
onChange={handleChange}
/>
I've tried several ways, like used Label with htmlFor, and used aria-label but not able to get rid of this warning.
Specifications I'm referencing:
WCAG 2.0 A
WCAG 2.1 A

"define this label in the resource bundle" bug sonarqube

I have several "define this label in the resource bundle" bug in my recent sonarqube scan
Here is a sample of a line of my code that gets this bug:
<p id="weekly" onclick="weeklyFilter()">Weekly</p>
Sonarqube suggests to transform it this way:
<label for="username"><fmt:message key="login.label.username" />:</label>
<input type="text" id="username" name="username">
Any suggestions on how to implement this for <p>
Thank you

after upgrading Google Chrome to version 63.0.3239.84 I have started receiving errors and warnings

after upgrading Google Chrome to version 63.0.3239.84 I have started receiving errors and warnings in console such as:
[DOM] Found 3 elements with non-unique id #SMTPSetting:
[DOM] Input elements should have autocomplete attributes (suggested: "current-password"):
[Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
Just add autocomplete attribute to inputs and the warnings will disappear. For example:
<div class="form-group">
<input type="email" class="form-control" autocomplete="email" required>
<input type="password" class="form-control" autocomplete="password" required>
</div>
If you don't have or just don't want to set value for the attribute autocomplete use autocomplete="foo" so that warning message disappears.
More information at: https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html
They appear to have added this option recently, which hides recommendations:
-source:recommendation
in the filter box.
Found it by accident. The filter box also support auto-complete with Ctrl+Space (Windows).

Meteor accounts - Custom login page

In Meteor, I am using accounts-base plugin for authentication system. Now, I need to create custom login page, how can I achieve it?
Here's the most basic html and js that will let you start your work. Put both files into client folder of your app.
client/login.html
<template name="login">
<h1>Custom login page for Aparna</h1>
<form>
<p>Email:</p>
<input type="email" name="email" id="email" /><br />
<p>Password:</p>
<input type="password" name="password" id="password" /><br />
<input type="submit" value="Submit" />
</form>
</template>
You'll need to include the login template into your main template, depending on where and how you want your login form implemented and which router you use.
client/login.js
Template.login.events({
'submit form': function(e) {
e.preventDefault();
var email = event.target.email.value;
var password = event.target.password.value;
Meteor.loginWithPassword(email, password);
}
});
You can see here that we use the function LoginWithPassword which is provided by accounts-password package.
I'll recommend you few good tutorials to extend this functionality:
Meteor custom login and signup form
Extending meteor users
Adding attributes to the user object when creating a new user
There's also an additional suite of Meteor packages called User Accounts that will do all that (and more) for you.

Selenium didn't find existing element

i create app that runs selenium internet explorer webdriver.
the program work fine on my pc but when i trying it with the same driver on other pc
its throws exception on the first element saying that it can't find it.
no frames in this html.
The first thing i checked is html pagesource the difference was:
on my pc:
<input name="cId" tabindex="1" id="CNum" type="text" size="13" maxlength="10" value="" autocomplete="off">
on other pc:
<INPUT tabIndex=2 id=CNum maxLength=10 size=13 name=cId autocomplete="off">
my selenium code:
driver.FindElement(By.Id("CNum")).SendKeys("123");
what can it be (the html source in other computer without type and in many cases without quotes.)
Thank you.
Try with
driver.FindElement(By.name("cId")).SendKeys("123"); or
driver.findelement(by.cssselector("input[name='cId']")).sendkeys("123");