Revert "fix(elements): correctly handle getting/setting properties before connecting the element (#36114)"
This reverts commit 363f14c893
because it is causing the side effects test to break on the
9.1.x branch.
This commit is contained in:
@ -94,22 +94,6 @@ if (browserDetection.supportsCustomElements) {
|
||||
expect(strategy.inputs.get('fooFoo')).toBe('foo-foo-value');
|
||||
expect(strategy.inputs.get('barBar')).toBe('barBar-value');
|
||||
});
|
||||
|
||||
it('should properly handle getting/setting properties on the element even if the constructor is not called',
|
||||
() => {
|
||||
// Create a custom element while ensuring that the `NgElementStrategy` is not created
|
||||
// inside the constructor. This is done to emulate the behavior of some polyfills that do
|
||||
// not call the constructor.
|
||||
strategyFactory.create = () => undefined as unknown as NgElementStrategy;
|
||||
const element = new NgElementCtor(injector);
|
||||
strategyFactory.create = TestStrategyFactory.prototype.create;
|
||||
|
||||
element.fooFoo = 'foo-foo-value';
|
||||
element.barBar = 'barBar-value';
|
||||
|
||||
expect(strategy.inputs.get('fooFoo')).toBe('foo-foo-value');
|
||||
expect(strategy.inputs.get('barBar')).toBe('barBar-value');
|
||||
});
|
||||
});
|
||||
}
|
||||
|
||||
|
Reference in New Issue
Block a user