feat(textarea): reflect disabled and readonly props#30910
feat(textarea): reflect disabled and readonly props#30910thetaPC merged 2 commits intoionic-team:feature-8.8from
Conversation
|
@KillerCodeMonkey is attempting to deploy a commit to the Ionic Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| await expect(page.locator('ion-range').first()).toHaveJSProperty('value', 50); | ||
| }); | ||
| test.describe('basic functionality', () => { | ||
| test('should have default values', async ({ page }) => { |
There was a problem hiding this comment.
It seems like a lot of changes but I only moved the tests under a describe.
| await expect(page.locator('#input-otp-note')).toHaveText('123'); | ||
| }); | ||
|
|
||
| test('should reflect props when component has a default value', async ({ page }) => { |
There was a problem hiding this comment.
This is the new test added.
| cy.get('ion-select').should('have.prop', 'value').and('eq', 'apples'); | ||
| }); | ||
| describe('basic functionality', () => { | ||
| it('should have default value', () => { |
There was a problem hiding this comment.
It seems like a lot of changes but I only moved the tests under a describe.
| cy.get('ion-select').should('have.prop', 'value').and('eq', 'apples'); | ||
| }); | ||
|
|
||
| it('should reflect props when component has a default value', () => { |
| }); | ||
|
|
||
| describe('basic functionality', () => { | ||
| it('should have default value', () => { |
There was a problem hiding this comment.
It seems like a lot of changes but I only moved the tests under a describe.
| cy.get('ion-select').should('have.prop', 'value').and('eq', 'apples'); | ||
| }); | ||
|
|
||
| it('should reflect props when component has a default value', () => { |
ShaneK
left a comment
There was a problem hiding this comment.
Looks good to me, left a few quickly fixable nits that are just minor cleanup I'm kind of surprised linting didn't catch
packages/angular/test/base/src/app/lazy/inputs/inputs.component.html
Outdated
Show resolved
Hide resolved
packages/angular/test/base/src/app/standalone/inputs/inputs.component.html
Outdated
Show resolved
Hide resolved
packages/angular/test/base/src/app/standalone/inputs/inputs.component.ts
Outdated
Show resolved
Hide resolved
a660675 to
4d9cd7a
Compare
|
Thank you for the PR! It'll be released in v8.8! |
Reflect
readonlyanddisabledproperties ation-textareahost element.Issue number: resolves #30911
What is the current behavior?
When setting readonly or disabled those settings are only reflected deep inside the ion-textarea component at the native textarea element.
Since there is no predefined readonly class it is hard to select readonly/disabled ion-textareas.
What is the new behavior?
Readonly and disabled props are reflected at ion-textarea host element.
Like they are for ion-inputs.
So it is consistent and will be helpful for easy element selection of disabled/readonly textareas (css, querySelector).
Does this introduce a breaking change?
Other information