Unequal strides support recently removed for DepthwiseConv2D
Hi @KaminiSabu, As it is mentioned in the documentation of Tensorflow versions [2.9](https://www.tensorflow.org/versions/r2.9/api_docs/python/tf/keras/layers/DepthwiseConv2D#args), [2.11](https://www.tensorflow.org/versions/r2.11/api_docs/python/tf/keras/layers/DepthwiseConv2D#args) and [2.12](https://www.tensorflow.org/versions/r2.12/api_docs/python/tf/keras/layers/DepthwiseConv2D#args) that the current implementation only supports equal length strides in the row and column dimensions. Specifying any stride value != 1 is incompatible with specifying any dilation_rate value != 1. describing the strides argument. This is an expected behavior in all the three versions of Tensorflow. Thank you!  Hello @synandi 

But in the link you shared, against strides, I can see the following entry for 2.9 and 2.11

"An integer or tuple/list of 2 integers, specifying the strides of the convolution along the height and width. Can be a single integer to specify the same value for all spatial dimensions. Specifying any stride value != 1 is incompatible with specifying any dilation_rate value != 1"

The nonavailability for equal stride support is mentioned only for 2.12

And more importantly, it works in the older installations on a specific machine and not on the new installations I am doing on other machines.

 @KaminiSabu Apologies for the confusion. You are right. It is not mentioned in 2.9 and 2.11 doc about the nonavailability for equal stride. Kindly refer to this [issue](https://github.com/keras-team/keras/issues/15667), it is a known issue. The document has been updated in TF v2.12. Thank you!   

  Ohh, so it should not work for any previous implementations as well. But it works in an older installation on a specific machine. Any idea how? Was the implementation wrong and hence is not being supported now? I used the same set of commands on that machine and got an output matrix printed:
```
import tensorflow as tf
import numpy as np
layer1 = tf.keras.layers.DepthwiseConv2D(depth_multiplier=2,kernel_size=(1,9),strides=(1,2))
print(layer1(np.ones((100, 28, 28, 1), dtype=np.float32)))
``` I'm not sure what has changed since 2.9 in the backend, but the current Argument details is inline with the API behavior.
For the latest API behavior, please install latest package. Thank you This issue is stale because it has been open for 7 days with no activity. It will be closed if no further activity occurs. Thank you. This issue was closed because it has been inactive for 7 days since being marked as stale. Please reopen if you'd like to work on this further. Are you satisfied with the resolution of your issue?
<a href="https://docs.google.com/forms/d/e/1FAIpQLSfaP12TRhd9xSxjXZjcZFNXPGk4kc1-qMdv3gc6bEP90vY1ew/viewform?entry.85265664=Yes&entry.2137816233=https://github.com/tensorflow/tensorflow/issues/60391">Yes</a>
<a href="https://docs.google.com/forms/d/e/1FAIpQLSfaP12TRhd9xSxjXZjcZFNXPGk4kc1-qMdv3gc6bEP90vY1ew/viewform?entry.85265664=No&entry.2137816233=https://github.com/tensorflow/tensorflow/issues/60391">No</a>

Please go to Stack Overflow for help and support:

https://stackoverflow.com/questions/tagged/tensorflow

If you open a GitHub issue, here is our policy:

1.  It must be a bug, a feature request, or a significant problem with the
    documentation (for small docs fixes please send a PR instead).
2.  The form below must be filled out.
3.  It shouldn't be a TensorBoard issue. Those go
    [here](https://github.com/tensorflow/tensorboard/issues).

**Here's why we have that policy**: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

------------------------

### System information

-   **Have I written custom code (as opposed to using a stock example script
    provided in TensorFlow)**: Yes
-   **OS Platform and Distribution (e.g., Linux Ubuntu 16.04)**: Ubuntu
-   **Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue
    happens on a mobile device**:
-   **TensorFlow installed from (source or binary)**:
-   **TensorFlow version (use command below)**: 2.9 and 2.11
-   **Python version**: 3.8
-   **Bazel version (if compiling from source)**:
-   **GCC/Compiler version (if compiling from source)**:
-   **CUDA/cuDNN version**: 11.2 and 8.1
-   **GPU model and memory**:
-   **Exact command to reproduce**:

import tensorflow as tf
import numpy as np
layer1 = tf.keras.layers.DepthwiseConv2D(depth_multiplier=2,kernel_size=(1,9),strides=(1,2))
print(layer1(np.ones((100, 28, 28, 1), dtype=np.float32)))

You can collect some of this information using our environment capture script:

https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh

You can obtain the TensorFlow version with:

```bash
python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
```

### Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.

The command would run without any error when I was using it with TF2.11 version installed previously. On the newly installed TF2.9 version, however, the code throws an error as:
InvalidArgumentError: Exception encountered when calling layer 'depthwise_conv2d_1' (type DepthwiseConv2D).
{{function_node __wrapped__DepthwiseConv2dNative_device_/job:localhost/replica:0/task:0/device:CPU:0}} Current implementation only supports equal length strides in the row and column dimensions. [Op:DepthwiseConv2dNative]
Call arguments received by layer 'depthwise_conv2d_1' (type DepthwiseConv2D):
  • inputs=tf.Tensor(shape=(100, 28, 28, 1), dtype=float32)

Seeing the documentation, the error is expected for version 2.12, but should work for versions 2.9 and 2.11
https://www.tensorflow.org/versions/r2.9/api_docs/python/tf/keras/layers/DepthwiseConv2D
https://www.tensorflow.org/versions/r2.11/api_docs/python/tf/keras/layers/DepthwiseConv2D
https://www.tensorflow.org/versions/r2.12/api_docs/python/tf/keras/layers/DepthwiseConv2D

Is it that the implementation existing in the earlier versions has been removed recently for all previous and current versions?

### Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
